Compared with 3.8.9: `ApolloClientOptions`, `DefaultOptions`, `QueryOptions`, `WatchQueryOptions`, `MutationOptions`, and 23 more. 27 newly deprecated.
@apollo/client 3.8.9 → 4.3.5: deprecates 28 API(s): from its source to your code
concat: Use `ApolloLink.from` instead. `concat` will be removed in a future major version.
GraphQLRequest: Use `ApolloLink.Request` instead
Operation: Use `ApolloLink.Operation` instead
FetchResult: Use `ApolloLink.Result` instead
RequestHandler: Use `ApolloLink.RequestHandler` instead
createSignalIfSupported: This is not used internally any more and will be removed in the next major version of Apollo Client.
createHttpLink: Use `HttpLink` from `@apollo/client/link/http` instead.
ApolloClient.disableNetworkFetches: `disableNetworkFetches` has been renamed to `prioritizeCacheValues`.
ApolloClient.readQuery: Tries to read some data from the store in the shape of the provided GraphQL query without making a network request. This method will start at the root query. To start at a specific id returned by `cache.identify` use `readFragment`. Pass the `optimistic` argument as part of the first argument instead of passing it as a separate option.
ApolloClient.readFragment: Tries to read some data from the store in the shape of the provided GraphQL fragment without making a network request. This method will read a GraphQL fragment from any arbitrary id that is currently cached, unlike `readQuery` which will only read from the root query. You must pass in a GraphQL document with a single fragment or a document with multiple fragments that represent what you are reading. If you pass in a document with multiple fragments then you must also specify a `fragmentName`. Pass the `optimistic` argument as part of the first argument instead of passing it as a separate optio
ApolloClient.reFetchObservableQueries: Refetches all of your active queries. `reFetchObservableQueries()` is useful if you want to bring the client back to proper state in case of a network outage It is important to remember that `reFetchObservableQueries()` _will_ refetch any active queries. This means that any components that might be mounted will execute their queries again using your network interface. If you do not want to re-execute any queries then you should make sure to stop watching any active queries. Takes optional parameter `includeStandby` which will include queries in standby-mode when refetching. Note: `cache-only`
Observable.subscribe: Instead of passing separate callback arguments, use an observer argument. Signatures taking separate callback arguments will be removed in v8. Details: https://rxjs.dev/deprecations/subscribe-arguments
Observable.forEach: Used as a NON-CANCELLABLE means of subscribing to an observable, for use with APIs that expect promises, like `async/await`. You cannot unsubscribe from this. **WARNING**: Only use this with observables you *know* will complete. If the source observable does not complete, you will end up with a promise that is hung up, and potentially all of the state of an async function hanging out in memory. To avoid this situation, look into adding something like {@link timeout }, {@link take }, {@link takeWhile }, or {@link takeUntil } amongst others. #### Example ```ts import { interval, take } from 'rxj
ApolloLink.concat: Combines multiple links into a single composed link. Use `ApolloLink.from` instead. `ApolloLink.concat` will be removed in a future major version.
HttpLink.concat: Combines multiple links into a single composed link. Use `ApolloLink.from` instead. `ApolloLink.concat` will be removed in a future major version.
registry.npmjs.orgquote checked
Nemotron fixes