Apollo 3 support
See original GitHub issueOverview
With the advent of Apollo 3, the ApolloClient
, some breaking changes were introduced, including centralization of imports and typedef changes.
These changes cause apps that have migrated to Apollo 3 and are currently using graphql-testing
to load additional packages that now are part of @apollo/client
.
That being said, I wanted to confirm that supporting Apollo 3 is something that’s on the roadmap and also offer to create a PR to perform the initial migration if that’s the case (and no one’s currently working on it).
Type
- New feature
- Changes to existing features
Motivation
Client apps that are consuming the library and have migrated to Apollo 3 will load additional packages on their dependency graph, such as:
- apollo-cache-inmemory
- apollo-client
- apollo-link
One additional example of a breaking change is that the GraphQL
type (from graphql-controller.ts
) is using the ApolloClient
type from apollo-client
, which doesn’t contain the setLink
method, now present in the Apollo client exported by @apollo/client
, causing errors when matching types from the library and this library.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
While we have our in-house non-Apollo solution, migrating to Apollo 3 is once on our short-term roadmap. Reopened this.
I made a fork of the graphql-testing library and updated it to work with Apollo 3. So far it’s working for us, but there could be some edge cases that needs updating. https://github.com/jcteague/graphql-testing