graphql-parser
graphql-parser copied to clipboard
A graphql query language and schema definition language parser and formatter for rust
Useful to reduce the size of payload
I have some schemas that have this directive location, and this crate currently crashes while trying to parse it.
added as_i32 backward-compatible feature flag to allow running to GraphQL spec here: https://graphql.org/learn/schema/#scalar-types
[This code](https://github.com/graphql-rust/graphql-parser/blob/8a759df14ff6a2d97b55bcbccad0a53ce0bee4a6/src/common.rs#L46) says that the spec doesn't have a size for numbers, but [it does](https://spec.graphql.org/draft/#sec-Int): > The Int scalar type represents a signed 32-bit numeric non-fractional value. Response formats that...
I will describe it soon
Closes #60
This PR exports `create::common` utils. Libraries that use `graphql_parser` often need to be able to deal with some raw values, so exposing `common` module can help and simplify some of...
GraphQL-JS (the reference implementation) implements the values as an array of key->value. This is done in order to allow parsing things like: ```graphql field(arg: { f: true, f: false })...
Fixes https://github.com/graphql-rust/graphql-parser/issues/25 Implementation is based upon the description here https://github.com/rust-unofficial/patterns/blob/master/patterns/visitor.md
As part of [juniper-from-schema][] I have made a [visitor trait](https://github.com/davidpdrsn/juniper-from-schema/blob/master/juniper-from-schema-code-gen/src/ast_pass/schema_visitor.rs) that handles walking over the schema AST. I'm thinking if it makes sense to move that trait upstream to here...