apollo-rs
apollo-rs copied to clipboard
apollographql
Spec compliant GraphQL Tools in Rust.
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. ## Awaiting Schedule These updates are awaiting their schedule. Click on a checkbox to...
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [annotate-snippets](https://togithub.com/rust-lang/annotate-snippets-rs) | dev-dependencies | minor | `0.10.0` -> `0.11.0` | --- ### Release...
When you mutate an executable document, fragments or variables that were previously in use may become unused. Currently the user is responsible for tracking this and pruning the now-unused definitions,...
Note: this is just about the implementation of the apollo-parser crate, and not relevant for end users. There's currently an internal kind-of footgun in apollo-parser: if you are parsing something...
We have a few places where we call `peek()` to check an upcoming token's kind, and then `peek_data().unwrap()` to check its value. For example, to identify what type of definition...
As found during https://github.com/apollographql/apollo-rs/pull/828. Current implementation: ```rust pub(crate) fn named_type(p: &mut Parser) { if let Some(TokenKind::Name) = p.peek() { let _g = p.start_node(SyntaxKind::NAMED_TYPE); name::name(p); } } ``` The caller has...
## Description I am trying to build a custom GraphQL validation tool using `apollo-compiler` v1.x beta. I like the Apollo implementation's soundness thanks to the tight Rust type system. However,...
apollo-compiler has several error enums, which for users ultimately only end up being accessed behind a `DiagnosticList` or `DiagnosticData`. We don't really use the different error enums for anything internally...
Add functionality to `apollo-smith` to generate an arbitrary number of subgraphs. This shouldn't compose them into a supergraph. I think it makes a bit more sense to have this api...
For historical reasons, a lot of the `apollo-smith` codebase is based on the parser. Now that the compiler is stabilising, we can unify the `apollo-compiler` and `apollo-smith` GraphQL representations, instead...