Skip to content
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

Comment in code is misleading or code is wrong for parsing query if its already AST #833

Closed
jardakotesovec opened this issue Feb 15, 2018 · 3 comments

Comments

@jardakotesovec
Copy link

jardakotesovec commented Feb 15, 2018

This is probably small catch - but maybe useful. Noticed that in here comment says if query is already an AST, don't parse or validate, but in fact it just skip the parsing step.

In our case it works as we want. Because we just want to do parse step outside of runHttpQuery to be able to read mutation name from it. But wanted to bring it up to make sure if it works as intended and the validation steps always happen there also in future.

@Piefayth
Copy link

Piefayth commented Mar 2, 2018

See also: #722 - Our use case prefers it works as described, not as written.

@Piefayth Piefayth mentioned this issue Mar 2, 2018
4 tasks
@martijnwalraven martijnwalraven moved this from To do to Needs Triage in New request pipeline Sep 27, 2018
@abernix
Copy link
Member

abernix commented Oct 22, 2018

We're working on providing techniques to control the exact behavior, which has been facilitated by the work done in #1795. For what it's worth, the confusing comment you'd referred to:

// if query is already an AST, don't parse or validate

...has been removed!

@abernix abernix closed this as completed Oct 22, 2018
New request pipeline automation moved this from Needs triage to Done Oct 22, 2018
@abernix
Copy link
Member

abernix commented Oct 22, 2018

We're working on providing techniques to control the exact behavior, which has been facilitated by the work done in #1795.

The confusing comment you'd referred to:

// if query is already an AST, don't parse or validate

...has been removed, so I'll close this. Thanks for reporting this originally!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

3 participants