-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Backport schema coordinates #4493
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
Conversation
14c3189 to
ab41972
Compare
|
Ping @magicmark , @phryneas, @yaacovCR, @Urigo, @benjie, @jerelmiller, can we get some 👀 on this PR ? |
magicmark
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yay! thanks!
jerelmiller
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me!
benjie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
Hello, I'm from the Prettier team. We want add support for this new ASTs introduced in this PR, but I'm not familiar with graphql, and there seems no test fixtures in this PR to generate these new nodes, I was not able to test. Can someone help us to solve prettier/prettier#18212 ? Thanks! |
|
@fisker this is a separate parser to parse schema-coordinates which are just strings like shown in the tests. This isn't an expansion of the main syntax like the executable descriptions are, I don't think any action from prettier is needed |
|
And to be clearer: schema coordinates only have one representation, there is no formatting (no spaces, commas, newlines), so definitely out of scope for prettier. |
|
@JoviDeCroock @benjie Thank you for the information! |
Backports #3044