-
Notifications
You must be signed in to change notification settings - Fork 700
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
Invalid type aliases generated on recursive types #3338
Comments
Thanks for the detailed report with reproduction case! I see what's going on here. We'll look into getting a fix out for this soon. |
Hello Anthony, any updates on this issue? This is still blocking us from updating apollo |
Hi Dominic. Thanks for letting us know that this is also blocking you. I'm working on a complex, high priority feature right now, so I'm not going to be able to get to this just yet, but I've marked this issue as high priority also and hope to dig into in as soon as I'm finished with what I'm working on. Can't give too great of an ETA until I get to research how to solve this. |
Sorry Anthony, Joel and I work together at M1. I was just trying to follow up on the status thank you for the update. And thank you for keeping an eye on this |
Summary
When fragments have a recursive structure, the generated type alias can become self-referencing and the module can't compile.
Version
1.9.0
Steps to reproduce the behavior
I've confirmed this behavior on 1.8.0 and 1.9.0. It seems to occur when using interfaces and multiple fragments on that interface.
schema.graphqls
GetLinks.gql
These two together generate this offending block:
For a complete reproduction of the bug, take a look at https://github.com/jmccance/apollographql-typealias-references-itself.
Logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: