Screenshot 2023-08-21 at 2.55.39 PM.png
# apollo-kotlin
j
Screenshot 2023-08-21 at 2.55.39 PM.png
m
You can use the non-relocated Gradle plugin, that will give you more insights. Replace
apollo-gradle-plugin
by
apollo-gradle-plugin-external
in your dependencies
Searching for keyField in GitHub search yields this result which in turns calls checkFieldSet, which contains a
!!
So looks like it's failing on line 77 there 🤔
Which seems to indicate that the field definition wasn't found for this particular field
Which is weird because this is supposed to be caught during validation earlier
But then the definition of a bug is that it is weird...
j
Yeah, that helps. I am looking at my type extensions and I might have added a
keyField
for a field that doesn’t exist.
m
Ah, that's interesting!
If you can share a reproducer, we should display a better error message
Or make this case completely impossible
j
Yeah, that fixed the build!
🎉 2
Thank you!
m
Sure thing! Do you mind opening an issue? We need to make a better error message for this
j
For sure. Would you need the entire schema or just the bit that I’m interacting with?
m
The more the better 😄
Hi @Jacob Rhoda 👋 circling back on this, did you get a chance to open the issue?
j
I had written an issue up and was waiting for approval from management to share that part of our schema. I finally have it but now my draft is gone! 😂
m
ahah oh no 😅 ! Sorry I didn't want to pull you in bureaucracy hell. Feel free to leave out the schema if it's too much of a hassle
j
thank you color 1