graphql-client
graphql-client copied to clipboard
graphql-rust
Typed, correct GraphQL requests and responses in Rust
Knowing what the generated types look like is harder than it should be at the moment. Maybe we could use the CLI to generate code, then rustdoc output since it's...
Just a reminder/placeholder for discussion on these two features. The extensions field is probably part of the standard (TODO: check), and would be easy to implement - maybe as an...
Since derive macros will now be imported (with `use`) in idiomatic code, we should provide the option to add imports to the generated module. Or maybe `use super::*` is a...
https://blog.apollographql.com/introducing-defer-in-apollo-server-f6797c4e9d6e This is not part of the spec. The parts that are not fetched yet could be `None`, and the patches would have that field as a root. How could...
I'm a bit of an outsider to Rust, but I've been interested in Yew and Juniper. I've had some experience finding different tools to generate TypeScript types through GraphQL introspection....
Schema path: based on .graphqlconfig Queries: expect a file named like the struct next to the rust file. This was suggested by @brainlessdeveloper This would be a fallback if the...
See this article for example: https://dev-blog.apollodata.com/why-you-might-want-a-graphql-client-e864050f789c
https://github.com/prismagraphql/graphql-config
I would be happy to have my (and others') pull requests code-reviewed, if anybody is interested please comment here to get mentioned when something needs reviewing.
It's probably a nice option to have, and it doesn't sound excessively hard to implement. Should it be an option, or the default?
Metadata
Owner
Metadata
Typed, correct GraphQL requests and responses in Rust