A modern programming language that makes developers happier.

kotlinlang

I upgraded to Apollo 3.7 and set up used coordinates, and ran into something which might be a bug, but I am not sure. Either way, it was interesting. Basically, given an `interface A { foo: X, bar: Y}` and a type that implements it `type B implements A { foo: X, baz: Z}`, and a `fragment F on A { foo, bar, ...on B { baz }}`, then `BBuilder` will only have a field for `baz` . Shouldn't `foo` and `bar` be also added to the builder? How else would you define their values? :smile:

Btw, my workaround was to re-write the fragment like `fragment F on A {  ...on B { foo, bar, baz }}`

Another workaround is to add the `B.foo` and `B.bar`coordinates to `alwaysGenerateTypesMatching`

oh, yeah. but I guess that the expected thing would be to have them added to the builder by default, no?

every interface field needs to pull all the implementation fields

We do have<https://github.com/apollographql/apollo-kotlin/blob/45521493137921985fd284f98081664a79e7affa/libraries/apollo-compiler/src/main/kotlin/com/apollographql/apollo3/compiler/ir/IrBuilder.kt#L612| some code though>...

Mmm this is done while merging the fields but not when computing used types from other modules

<https://github.com/apollographql/apollo-kotlin/pull/4506/files>

If that works for you, we'll make a patch release

I can test it tomorrow, for now I went with your suggested workaround :slightly_smiling_face:

Hmm, I am trying to run `publishToMavenLocal`, but I get a bunch of errors:
```* What went wrong:
Script compilation errors:

  Line 001: import JapiCmp.configureJapiCmp
                   ^ Unresolved reference: JapiCmp

  Line 094:     checkGitStatus()
                ^ Unresolved reference: checkGitStatus

  Line 119: rootProject.configureNode()
                        ^ Unresolved reference: configureNode

  Line 120: rootProject.configureJapiCmp()
                        ^ Unresolved reference: configureJapiCmp```
Any idea what could be wrong? :disappointed:

It seems like Gradle doesn't pick up `build-logic` :confused:

(I'm at `adccf1360de92d00e7ce93d4c5a825532f310769` )

same: `Your branch is up to date with 'origin/fix-used-coordinates-on-interfaces'.`

```openjdk version "11.0.11" 2021-04-20
OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)
OpenJDK 64-Bit Server VM AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode)```
Intel Mac, if it matters

I've seen it a couple of times where the build-logic jar becomes empty

well, that didn't help. build-logic.jar gets regenerated, but it's only 884 bytes, is that normal?

unzipped it, it only has MANIFEST.MF inside it :see_no_evil:

`--rerun-tasks` did the trick :slightly_smiling_face: thanks!
I will let it build, and try it out after lunch

Ok, can confirm, the fix works well :slightly_smiling_face:

Nice, thanks for confirming! Will do a patch on Monday