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
Defining queries using structured data #32
Comments
GraphQL queries are well-defined, and given the (strongly typed) schema they can be checked for syntactic and semantic errors, unlike the JSON objects. GraphQL queries are thus less error prone (at least in theory). Check out eslint-plugin-graphql for an example of what's possible with GraphQL. And that's really just the beginning. |
Closing since no activity for 2 weeks. Feel free to reopen to continue the discusssion. |
Update operation registry plugin to use manifest v2
Update operation registry plugin to use manifest v2
Update operation registry plugin to use manifest v2
I'm just exploring graphql and see existing way of doing requests from client is using string based queries. I see such approach as kinda error prone and unstructured. What are the advantages of this? Do you see any advantages (or maybe obvious disadvantages) if there would be a way in defining queries using
json
object instead of string?Kind of:
Also I see thy way of defining schema using string based approach is too kind of error prone.
The text was updated successfully, but these errors were encountered: