urql

Patch Changes

• Update build process to generate correct source maps
  Submitted by @kitten (See #3201)

Minor Changes

• Add globalIDs configuration option to omit typenames in cache keys
  Submitted by @kitten (See #3224)

Patch Changes

• Update build process to generate correct source maps
  Submitted by @kitten (See #3201)
• Prevent offlineExchange from issuing duplicate operations
  Submitted by @kitten (See #3200)
• ⚠️ Fix reference equality not being preserved. This is a fix on top of #3165, and was previously not addressed to avoid having to test for corner cases that are hard to cover. If you experience issues with this fix, please let us know
  Submitted by @kitten (See #3228)
• Retry operations against offline cache and stabilize timing of flushing failed operations queue after rehydrating the storage data
  Submitted by @kitten (See #3196)

Patch Changes

• Update build process to generate correct source maps
  Submitted by @kitten (See #3201)

Minor Changes

• Reset retryExchange’s previous attempts and delay if an operation succeeds. This prevents the exchange from keeping its old retry count and delay if the operation delivered a result in the meantime. This is important for it to help recover from failing subscriptions
  Submitted by @kitten (See #3229)

Patch Changes

• Update build process to generate correct source maps
  Submitted by @kitten (See #3201)

Patch Changes

• Update build process to generate correct source maps
  Submitted by @kitten (See #3201)

Patch Changes

• ⚠️ Fix missing cache updates, when a query that was previously torn down restarts and retrieves results from the cache. In this case a regression caused cache updates to not be correctly applied to the queried results, since the operation wouldn’t be recognised properly
  Submitted by @kitten (See #3193)

Major Changes

• Update the preferGetForPersistedQueries option to include the 'force' and 'within-url-limit' values from the Client's preferGetMethod option. The default value of true no longer sets OperationContext's preferGetMethod setting to 'force'. Instead, the value of preferGetForPersistedQueries carries through to the OperationContext's preferGetMethod setting for persisted queries
  Submitted by @NWRichmond (See #3192)

Patch Changes

• Avoid unnecessary re-render when two components use the same query but receive unchanging results, due to differing operations
  Submitted by @nathan-knight (See #3195)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)

Patch Changes

• Publish with npm provenance
  Submitted by @kitten (See #3180)