A modern programming language that makes developers happier.

kotlinlang

For my tests, to make a fake resolver I had a call to  `private val delegate = DefaultFakeResolver(__Schema.all)`, but after upgrading to 4.0 I don't seem to get the `all` generated anymore. Is it some extra configuration now perhaps? :eyes:

hmm if you have `generateDataBuilders.set(true)`  this should be generated

I do have that as true. Did you see the same in your apollo-4 testing branch btw? Because that's what I was looking at right now and I am experiencing this.

no I didn't have any compilation error, I could run the app!

Right, this was only in the test sources, the app runs fine for me too. This delegate only exists for some tests we got.
Perhaps this plays a role here too hmm

ohhhh tests :sweat_smile: Didn't think of running them

Hehe yeah dw about it. Is there a specific task I should be running which is supposed to generate this __Schema class? I assume it's just `generateApolloSources` right? I am trying to tweak things in the gradle config and run it to see if anything changes

I think it's just the wrong import: it should be `import octopus.schema.__Schema`

ah yes that's <https://www.apollographql.com/docs/kotlin/v4/migration/4.0/#__schema-is-in-the-schema-subpackage|a change in 4.x>

(:eyes:  maybe the migration helper could update this automatically)

Ahh there it is, thanks so much!
Yes, that would be great for the migration helper to do this! If there are no concerns that old references to it were actually intentionally pointing to the other __Schema class?

The import which worked for me ended up being
```import octopus.schema.__Schema```
Where `octopus` is the service name.
The docs show:
```// Replace
import com.example.type.__Schema

// With
import data.builders.schema.__Schema```
Is the `data.builders` the placeholder there for whatever the service name would be? If I didn't have the IDE auto-importing this for me I wouldn't have realized this myself I think.

Hmm I think it should be `com.example` in the docs

&gt; If there are no concerns that old references to it were actually intentionally pointing to the other __Schema class?
&gt; 
That's a good question! :eyes: