-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Absinthe 1.7.7 mix absinthe.schema.sdl
breaks when using absinthe_relay
connections
#1328
Comments
As noted, I have a workaround, but it feels weird that I have to explicitly declare the edges for the case where I am generating the SDL. This is not required or showing any errors during normal compile (but I’m not sure whether the references exists pass is done during compile). |
Hey have you tried using main? There was a bug fix that may be related to this. |
I had not tried main. #1326 does fix this issue. Probably worth putting in the release notes when released, as the "workarounds" didn't actually work, they just seemed to work by suppressing the errors and not actually resolving anything. |
Looking forward to 1.7.8 when released. |
As a related issue, if you use
It looks like This is a breaking error, hopefully a patch release can be published soon. |
v1.7.8 has been pushed with this fix. |
Environment
Expected behavior
I’m still trying to figure out how to create a minimal reproduction as well as figure out a potential fix, but I wanted to raise this ASAP in case someone else has seen it or has an idea on how to better test it and/or resolve it.
Given a Relay schema (we use modern) that looks something like this (super simplified):
With Absinthe 1.7.6,
mix absinthe.schema.sdl
generates the appropriateschema.graphql
. With Absinthe 1.7.7,mix absinthe.schema.sdl
fails to generate the schema. Modifying the generator to inspect the output includes anAbsinthe.Phase.Error
:If, however, I modify the schema to be:
The
foo_edge
is defined again and the SDL is generated again.The text was updated successfully, but these errors were encountered: