apollo-rs
apollo-rs copied to clipboard
apollographql
Spec compliant GraphQL Tools in Rust.
- [ ] validate fragment name uniqueness, [spec](https://spec.graphql.org/October2021/#sec-Fragment-Name-Uniqueness) - [ ] validate fragment spread type existence, [spec](https://spec.graphql.org/October2021/#sec-Fragment-Spread-Type-Existence) - [ ] validate fragments on composite types, [spec](https://spec.graphql.org/October2021/#sec-Fragments-On-Composite-Types) - [ ] validate...
implement leaf field selection [spec](https://spec.graphql.org/October2021/#sec-Leaf-Field-Selections)
implement field selection merging, [spec](https://spec.graphql.org/October2021/#sec-Field-Selection-Merging). in the compiler's db, fields should likely still be separated, but have an api that provides access to the merged field selection which is to...
check that fields in subscription selection set are not introspection fields. [spec](https://spec.graphql.org/October2021/#sel-FALPHDGDDLAAADFBA04c)
We want to be able to test some wildly incorrect graphql input and ensure the parser, and the compiler, and any other tools that might use these two crates are...
To further help with fuzzing and catching inconsistencies in stream and defer implementations, consider adding specific test-case generation for stream and defer. Perhaps also go all in and add tag/inaccessible/join?
I don't want to be the one doing all the publishings in perpetuity! We've got a bot for that :)
This is one of the router's usecases. Let's say we have a schema like this: ```graphql type Query { me: String } interface Foo { me: String } interface Bar...
We can set a recursion limit API in the parser, and this should be carried forward to the compiler's API.
Fixes https://github.com/apollographql/apollo-rs/issues/180
