You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey Jan, thanks for thee hint! This seems like a slightly bigger refactor since assertTypeWithFields is used in multiple places, I'm not really comfortable doing that right now. I'll be releasing a getting started tutorial about Relay Modern today where I adjust the schema and remove the constraint for certain fields to be required in order to work around the issue.
nikolasburk
changed the title
[Modern] Compiler doesn't work for @connection directive when types are non-nullable
[Modern] Compiler doesn't work for connections when types are non-nullable
Jul 1, 2017
nikolasburk
changed the title
[Modern] Compiler doesn't work for connections when types are non-nullable
[relay-compiler] Compiler doesn't work for connections when types are non-nullable
Jul 1, 2017
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I'm having an issue with the
relay-compiler
that fails when fields are required.Here's a simplified version of the schema that I used when I was hitting the issue.
Using required fields on the connections caused the compiler to fail with the following error:
Using the following schema without required fields works:
Feel free to take a look at the full project (note that the README doesn't yet include instructions about setting up the
relay-compiler
).The text was updated successfully, but these errors were encountered: