urql

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Remove closure-compiler from the build step (See #1570)
• Updated dependencies (See #1570, #1509, #1600, and #1515)
  • @urql/[email protected]

Patch Changes

• Add Storybook metadata to package.json for npm discoverability, by @coderkevin (See #1469)

Patch Changes

• Prevent the refocus Exchange from being used on a Node env, by @JoviDeCroock (See #1430)

Patch Changes

• Add a displayName to the Provider, by @JoviDeCroock (See #1431)

Patch Changes

• Allow mutation to accept a more partial GraphQLRequest object without a key or variables, by @JoviDeCroock (See #1473)

Patch Changes

• Ensure urqlState is hydrated onto the client when a user opts out of ssr and uses the getServerSideProps or getStaticProps on a page-level and withUrqlClient is wrapped on an _app level.
  Examples:
  • getStaticProps
  • getServerSideProps, by @JoviDeCroock (See #1501)

Patch Changes

• Add a displayName to the Provider, by @JoviDeCroock (See #1431)

Patch Changes

• ⚠️ Fix issue where useSubscription would endlessly loop when the callback wasn't memoized, by @JoviDeCroock (See #1384)
• ⚠️ Fix case where identical useQuery calls would result in cross-component updates, by @JoviDeCroock (See #1383)

Minor Changes

• Update minifyIntrospectionQuery utility to remove additional information on arguments and to filter out schema metadata types, like __Field and others, by @kitten (See #1351)

Minor Changes

• Breaking: Remove pollInterval option from useQuery. Please consider adding an interval manually calling executeQuery(), by @kitten (See #1374)
• Remove deprecated operationName property from Operations. The new Operation.kind property is now preferred. If you're creating new operations you may also use the makeOperation utility instead.
  When upgrading @urql/core please ensure that your package manager didn't install any duplicates of it. You may deduplicate it manually using npx yarn-deduplicate (for Yarn) or npm dedupe (for npm), by @kitten (See #1357)

Patch Changes

• Updated dependencies (See #1374, #1357, and #1375)
  • @urql/[email protected]

Patch Changes

• Updated dependencies (See #1335, #1357, and #1374)
  • [email protected]

Major Changes

• Breaking: Remove pollInterval option from useQuery. Instead please consider using useEffect calling executeQuery on an interval, by @kitten (See #1374)

Minor Changes

• Reimplement useQuery to apply a consistent Suspense cache (torn down queries will still eliminate stale values) and support all Concurrent Mode edge cases. This work is based on useMutableSource's mechanisms and allows React to properly fork lanes since no implicit state exists outside of useState in the implementation. The useSubscription hook has been updated similarly without a cache or retrieving values on mount, by @kitten (See #1335)
• Remove deprecated operationName property from Operations. The new Operation.kind property is now preferred. If you're creating new operations you may also use the makeOperation utility instead.
  When upgrading @urql/core please ensure that your package manager didn't install any duplicates of it. You may deduplicate it manually using npx yarn-deduplicate (for Yarn) or npm dedupe (for npm), by @kitten (See #1357)

Patch Changes

• Updated dependencies (See #1374, #1357, and #1375)
  • @urql/[email protected]

Minor Changes

• Remove deprecated operationName property from Operations. The new Operation.kind property is now preferred. If you're creating new operations you may also use the makeOperation utility instead.
  When upgrading @urql/core please ensure that your package manager didn't install any duplicates of it. You may deduplicate it manually using npx yarn-deduplicate (for Yarn) or npm dedupe (for npm), by @kitten (See #1357)

Patch Changes

• Updated dependencies (See #1374, #1357, and #1375)
  • @urql/[email protected]

Major Changes

• Add improved error awareness to Graphcache. When Graphcache now receives a GraphQLError (via a CombinedError) it checks whether the GraphQLError's path matches up with null values in the data. Any null values that the write operation now sees in the data will be replaced with a "cache miss" value (i.e. undefined) when it has an associated error. This means that errored fields from your GraphQL API will be marked as uncached and won't be cached. Instead the client will now attempt a refetch of the data so that errors aren't preventing future refetches or with schema awareness it will attempt a refetch automatically. Additionally, the updates functions will now be able to check whether the current field has any errors associated with it with info.error, by @kitten (See #1356)

Minor Changes

• Allow schema option to be passed with a partial introspection result that only contains queryType, mutationType, and subscriptionType with their respective names. This allows you to pass { __schema: { queryType: { name: 'Query' } } } and the likes to Graphcache's cacheExchange to alter the default root names without enabling full schema awareness, by @kitten (See #1379)

Patch Changes

• Updated dependencies (See #1374, #1357, and #1375)
  • @urql/[email protected]

Major Changes

• Breaking: Remove pollInterval option from useQuery. Instead please consider using useEffect calling executeQuery on an interval, by @kitten (See #1374)

Minor Changes

• Remove deprecated operationName property from Operations. The new Operation.kind property is now preferred. If you're creating new operations you may also use the makeOperation utility instead.
  When upgrading @urql/core please ensure that your package manager didn't install any duplicates of it. You may deduplicate it manually using npx yarn-deduplicate (for Yarn) or npm dedupe (for npm), by @kitten (See #1357)

Patch Changes

• Updated dependencies (See #1374, #1357, and #1375)
  • @urql/[email protected]

Major Changes

• Breaking: Remove pollInterval feature from OperationContext. Instead consider using a source that uses Wonka.interval and Wonka.switchMap over client.query()'s source, by @kitten (See #1374)
• Remove deprecated operationName property from Operations. The new Operation.kind property is now preferred. If you're creating new operations you may also use the makeOperation utility instead.
  When upgrading @urql/core please ensure that your package manager didn't install any duplicates of it. You may deduplicate it manually using npx yarn-deduplicate (for Yarn) or npm dedupe (for npm), by @kitten (See #1357)

Minor Changes

• Reemit an OperationResult as stale: true if it's being reexecuted as network-only operation to give bindings immediate feedback on background refetches, by @kitten (See #1375)

Minor Changes

• Add enforcePersistedQueries option to persistedFetchExchange, which disables automatic persisted queries and retry logic, and instead assumes that persisted queries will be handled like normal GraphQL requests, by @kitten (See #1358)

Patch Changes

• Updated dependencies (See #1374, #1357, and #1375)
  • @urql/[email protected]

Patch Changes

• ⚠️ Fix non-query operations being upgraded by requestPolicyExchange and time being stored by last issuance rather than last result, by @kitten (See #1377)
• Updated dependencies (See #1374, #1357, and #1375)
  • @urql/[email protected]

Patch Changes

• Add a workaround for graphql-tag/loader, which provides filtered query documents (where the original document contains multiple operations) without updating or providing a correct document.loc.source.body string, by @kitten (See #1315)