apollo-feature-requests
apollo-feature-requests copied to clipboard
๐งโ๐ Apollo Client Feature Requests | (no ๐ please).
Preface: I saw [this issue](https://github.com/apollographql/react-apollo/pull/2710) which seems to have implemented the equivalent for Mutations. ## The problem I have a menu that opens up when clicked on. Similar to this:...
# cache.modify - Expose args passed to field modified fields What I am hoping to accomplish with this feature request may already exist in some form and maybe I am...
### Problem Description FieldPolicy ['read' functions](https://www.apollographql.com/docs/react/caching/cache-field-behavior/#the-read-function) can not be asynchronous (I think?). For example, if I write something like the snippet below, a query that uses the field `todos` as...
# Allow `SchemaLink.Options.schema` as async function I am using [type-graphql][1] with apollo server and for SSR apollo client I want to use it `SchemaLink`. `type-graphql` gives a `async` method to...
Refactoring of fetch policy types in apollo-client to exported constants to reduce error possibility
Instead of of having to use this option as a string: - `fetchPolicy: 'cache-first'` It would be better for error reduction if the FetchPolicy was refactored to use constants and...
Currently, modifying a non-root, non-normalized field requires nesting calls to `cache.modify()`, like the below code modifying `ROOT_QUERY.currentUser.favoriteReviews`: ``` const [removeReview] = useMutation(REMOVE_REVIEW_MUTATION, { update: (cache) => { cache.modify({ fields: {...
It would be great to support BSON / EJSON for communications because this is able to preserve additional types of values, like date, buffer, and integer. The project(s) wouldn't necessarily...
We have a mixed application that uses Apollo Client for both React and non-react code. Testing React code is easy and convenient given the exported and documented `MockedProvider` utility, however,...
My field policy `merge` is built for pagination and puts things on the end of the list. My `objectAdded` `subscribeToMore` should put new things at the beginning of the list....
### Context Per [this issue](https://github.com/apollographql/apollo-client/issues/7311), here is the current behavior in a React component's lifecycle when using `fetchPolicy` and `nextFetchPolicy`: 1. Component A mounts, all queries within this component tree...