kitten.sh
+6
-6
.github/CODEOWNERS
+6
-6
.github/CODEOWNERS
+2
-2
.github/ISSUE_TEMPLATE/bug_report.yaml
+2
-2
.github/ISSUE_TEMPLATE/bug_report.yaml
···-- label: I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which [GitHub Discussions](https://github.com/FormidableLabs/urql/discussions) should be used-- label: Follow our [Code of Conduct](https://github.com/FormidableLabs/urql/blob/main/CODE_OF_CONDUCT.md)
···+- label: I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which [GitHub Discussions](https://github.com/urql-graphql/urql/discussions) should be used+- label: Follow our [Code of Conduct](https://github.com/urql-graphql/urql/blob/main/CODE_OF_CONDUCT.md)
+1
-1
.github/ISSUE_TEMPLATE/config.yml
+1
-1
.github/ISSUE_TEMPLATE/config.yml
+3
-3
CODE_OF_CONDUCT.md
+3
-3
CODE_OF_CONDUCT.md
···
···
+6
-7
CONTRIBUTING.md
+6
-7
CONTRIBUTING.md
···-- If you have a question, try [creating a GitHub Discussions thread.](https://github.com/FormidableLabs/urql/discussions/new)-- If you think you've found a bug, [open a new issue.](https://github.com/FormidableLabs/urql/issues/new/choose)-- or, if you found a bug you'd like to fix, [open a PR.](https://github.com/FormidableLabs/urql/compare)-- If you'd like to propose a change [open an RFC issue.](https://github.com/FormidableLabs/urql/issues/new?labels=future+%F0%9F%94%AE&template=RFC.md&title=RFC%3A+Your+Proposal) You can read more about the RFC process [below](#how-do-i-propose-changes).···We follow an **RFC proposal process**. This allows anyone to propose a new feature or a change, and-All RFCs are added to the [RFC Lifecycle board.](https://github.com/FormidableLabs/urql/projects/3)This board tracks where an RFC stands and who's working on it until it's completed. Bugs and PRs mayend up on there too if no corresponding RFC exists or was necessary. RFCs are typically first addedto "In Discussion" until we believe they're ready to be worked on. This step may either be short,···
···+- If you have a question, try [creating a GitHub Discussions thread.](https://github.com/urql-graphql/urql/discussions/new)+- If you think you've found a bug, [open a new issue.](https://github.com/urql-graphql/urql/issues/new/choose)+- or, if you found a bug you'd like to fix, [open a PR.](https://github.com/urql-graphql/urql/compare)+- If you'd like to propose a change [open an RFC issue.](https://github.com/urql-graphql/urql/issues/new?labels=future+%F0%9F%94%AE&template=RFC.md&title=RFC%3A+Your+Proposal) You can read more about the RFC process [below](#how-do-i-propose-changes).···We follow an **RFC proposal process**. This allows anyone to propose a new feature or a change, and+All RFCs are added to the [RFC Lifecycle board.](https://github.com/urql-graphql/urql/projects/3)This board tracks where an RFC stands and who's working on it until it's completed. Bugs and PRs mayend up on there too if no corresponding RFC exists or was necessary. RFCs are typically first addedto "In Discussion" until we believe they're ready to be worked on. This step may either be short,···
+2
-1
LICENSE
+2
-1
LICENSE
+13
-12
README.md
+13
-12
README.md
···-<img alt="CI Status" src="https://github.com/FormidableLabs/urql/actions/workflows/ci.yml/badge.svg?branch=main" />···<img alt="GitHub Discussions: Chat With Us" src="https://badgen.net/badge/discussions/chat%20with%20us/purple" />···- 🌱 Normalized caching via [`@urql/exchange-graphcache`](https://formidable.com/open-source/urql/docs/graphcache)- 🔬 Easy debugging with the [`urql` devtools browser extensions](https://formidable.com/open-source/urql/docs/advanced/debugging/)-`urql` is a GraphQL client that exposes a set of helpers for several frameworks. It's built to be highly customisable and versatile so you can take it from getting started with your first GraphQL project all the way to building complex apps and experimenting with GraphQL clients.-While GraphQL is an elegant protocol and schema language, client libraries today typically come with large API footprints. We aim to create something more lightweight instead.···The documentation contains everything you need to know about `urql`, and contains several sections in order of importance···- **[API](https://formidable.com/open-source/urql/docs/api/)** — the API documentation for each individual package.-**Active:** Formidable is actively working on this project, and we expect to continue work on this project for the foreseeable future. Bug reports, feature requests and pull requests are welcome.
···+<img alt="CI Status" src="https://github.com/urql-graphql/urql/actions/workflows/ci.yml/badge.svg?branch=main" />···<img alt="GitHub Discussions: Chat With Us" src="https://badgen.net/badge/discussions/chat%20with%20us/purple" />···- 🌱 Normalized caching via [`@urql/exchange-graphcache`](https://formidable.com/open-source/urql/docs/graphcache)- 🔬 Easy debugging with the [`urql` devtools browser extensions](https://formidable.com/open-source/urql/docs/advanced/debugging/)+`urql` is a GraphQL client that exposes a set of helpers for several frameworks. It's built to be highly customisable and versatile so+you can take it from getting started with your first GraphQL project all the way to building complex apps and experimenting with GraphQL clients.+**📃 For more information, [check out the docs](https://formidable.com/open-source/urql/docs/).**···+**The urql project was founded by [Formidable](https://formidable.com/) and is actively developed+If you'd like to get involved, [check out our Contributor's guide.](https://github.com/urql-graphql/urql/blob/main/CONTRIBUTING.md)The documentation contains everything you need to know about `urql`, and contains several sections in order of importance···- **[API](https://formidable.com/open-source/urql/docs/api/)** — the API documentation for each individual package.
+1
-1
docs/advanced/README.md
+1
-1
docs/advanced/README.md
···- [**Server-side Rendering**](./server-side-rendering.md) guides us through how to set up server-side rendering and rehydration.-devtools](https://github.com/FormidableLabs/urql-devtools/) and how to add our own debug events- [**Retrying operations**](./retry-operations.md) shows the `retryExchange` which allows you to retry operations when they've failed.- [**Authentication**](./authentication.md) describes how to implement authentication using the `authExchange`
···- [**Server-side Rendering**](./server-side-rendering.md) guides us through how to set up server-side rendering and rehydration.- [**Retrying operations**](./retry-operations.md) shows the `retryExchange` which allows you to retry operations when they've failed.- [**Authentication**](./authentication.md) describes how to implement authentication using the `authExchange`
+2
-2
docs/advanced/debugging.md
+2
-2
docs/advanced/debugging.md
···-It's easiest to debug `urql` with the [`urql` devtools.](https://github.com/FormidableLabs/urql-devtools/)It offers tools to inspect internal ["Debug Events"](#debug-events) as they happen, to explore data
···+It's easiest to debug `urql` with the [`urql` devtools.](https://github.com/urql-graphql/urql-devtools/)It offers tools to inspect internal ["Debug Events"](#debug-events) as they happen, to explore data
+1
-1
docs/api/auth-exchange.md
+1
-1
docs/api/auth-exchange.md
+1
-1
docs/architecture.md
+1
-1
docs/architecture.md
···- [`requestPolicyExchange`](./api/request-policy-exchange.md): Automatically upgrades `cache-only` and `cache-first` operations to `cache-and-network` after a given amount of time.-- `devtoolsExchange`: Provides the ability to use the [urql-devtools](https://github.com/FormidableLabs/urql-devtools)We can even swap out our [document cache](./basics/document-caching.md), which is implemented by
···- [`requestPolicyExchange`](./api/request-policy-exchange.md): Automatically upgrades `cache-only` and `cache-first` operations to `cache-and-network` after a given amount of time.+- `devtoolsExchange`: Provides the ability to use the [urql-devtools](https://github.com/urql-graphql/urql-devtools)We can even swap out our [document cache](./basics/document-caching.md), which is implemented by
+5
-5
docs/basics/ui-patterns.md
+5
-5
docs/basics/ui-patterns.md
···-> This page is incomplete. You can help us expanding it by suggesting more patterns or asking us about common problems you're facing on [GitHub Discussions](https://github.com/FormidableLabs/urql/discussions).Generally, `urql`'s API surface is small and compact. Some common problems that we're facing when building apps may look like they're not a built-in feature, however, there are several patterns that even a lean UI can support.This page is a collection of common UI patterns and problems we may face with GraphQL and how we can tackle them in···-list that constantly changes. [You can find a full code example of this pattern in our example folder on the topic of Graphcache pagination.](https://github.com/FormidableLabs/urql/tree/main/examples/with-graphcache-pagination)-We also do not need to use our normalized cache to achieve this. As long as we're able to split individual lists up into chunks across components, we can also solve this problem entirely in UI code. [Read our example code on how to achieve this.](https://github.com/FormidableLabs/urql/tree/main/examples/with-pagination)···When we want to introduce one of these patterns we add the package and add it to the `exchanges`
···+> This page is incomplete. You can help us expanding it by suggesting more patterns or asking us about common problems you're facing on [GitHub Discussions](https://github.com/urql-graphql/urql/discussions).Generally, `urql`'s API surface is small and compact. Some common problems that we're facing when building apps may look like they're not a built-in feature, however, there are several patterns that even a lean UI can support.This page is a collection of common UI patterns and problems we may face with GraphQL and how we can tackle them in···+list that constantly changes. [You can find a full code example of this pattern in our example folder on the topic of Graphcache pagination.](https://github.com/urql-graphql/urql/tree/main/examples/with-graphcache-pagination)+We also do not need to use our normalized cache to achieve this. As long as we're able to split individual lists up into chunks across components, we can also solve this problem entirely in UI code. [Read our example code on how to achieve this.](https://github.com/urql-graphql/urql/tree/main/examples/with-pagination)···When we want to introduce one of these patterns we add the package and add it to the `exchanges`
+23
-34
docs/comparison.md
+23
-34
docs/comparison.md
···-| ------------------------------------------ | ----------------------------------- | --------------------------------------------- | ------------------------------ |-| Base Bundle Size | **5.9kB** (7.1kB with bindings) | 32.9kB | 27.7kB (34.1kB with bindings) |-| Persisted Queries | ✅ `@urql/exchange-persisted-fetch` | ✅ `apollo-link-persisted-queries` | ✅ |-| Defer & Stream Directives | ✅ | ✅ / 🛑 (`@defer` is supported in >=3.7.0, `@stream` is not yet supported) | 🟡 (unreleased) |-| Retrying Failed Queries | ✅ `@urql/exchange-retry` | ✅ `apollo-link-retry` | ✅ `DefaultNetworkLayer` |-| Easy Authentication Flows | ✅ `@urql/exchange-auth` | 🛑 (no docs for refresh-based authentication) | 🟡 `react-relay-network-layer` |matter which framework you use it with. It's worth mentioning that all three clients support some···One thing of note is our lack of support for batched queries in `urql`. We explicitly decided not to-packages](https://github.com/FormidableLabs/urql/issues/800#issuecomment-626342821) as the benefitsare not present anymore in most cases with HTTP/2 and established patterns by Relay that recommend···-Interestingly all three libraries heavily support React as they were all started from the React-community outwards, but Apollo and Vue benefit from community bindings for different frameworks a-Apollo's `vue-apollo` in the short term, we're aiming for first-party support for these bindings.-This is a common criticism that we hear about `urql`, and it's true that our community isn't as-investment, and good documentation. So you may have to evaluate whether you can get any questions-answered quickly enough on [GitHub Discussions](https://github.com/FormidableLabs/urql/discussions)
···+| ------------------------------------------ | ----------------------------------- | -------------------------------------------------------------------------- | ------------------------------ |+| Base Bundle Size | **5.9kB** (7.1kB with bindings) | 32.9kB | 27.7kB (34.1kB with bindings) |+| Persisted Queries | ✅ `@urql/exchange-persisted-fetch` | ✅ `apollo-link-persisted-queries` | ✅ |+| Defer & Stream Directives | ✅ | ✅ / 🛑 (`@defer` is supported in >=3.7.0, `@stream` is not yet supported) | 🟡 (unreleased) |+| Retrying Failed Queries | ✅ `@urql/exchange-retry` | ✅ `apollo-link-retry` | ✅ `DefaultNetworkLayer` |+| Easy Authentication Flows | ✅ `@urql/exchange-auth` | 🛑 (no docs for refresh-based authentication) | 🟡 `react-relay-network-layer` |matter which framework you use it with. It's worth mentioning that all three clients support some···One thing of note is our lack of support for batched queries in `urql`. We explicitly decided not to+packages](https://github.com/urql-graphql/urql/issues/800#issuecomment-626342821) as the benefitsare not present anymore in most cases with HTTP/2 and established patterns by Relay that recommend···
+1
-1
docs/graphcache/errors.md
+1
-1
docs/graphcache/errors.md
···warning. This may happen because you've used the default reserved names `Mutation` or `Subscription`for entities rather than as special Operation Root Types, and haven't specified this in the schema.-[Schema Awareness](https://formidable.com/open-source/urql/docs/graphcache/schema-awareness/) or by
···warning. This may happen because you've used the default reserved names `Mutation` or `Subscription`for entities rather than as special Operation Root Types, and haven't specified this in the schema.
+3
-3
docs/graphcache/offline.md
+3
-3
docs/graphcache/offline.md
···-Before installing the [library](https://github.com/FormidableLabs/urql/tree/main/packages/storage-rn), ensure you have installed the necessary peer dependencies:- NetInfo ([RN](https://github.com/react-native-netinfo/react-native-netinfo) | [Expo](https://docs.expo.dev/versions/latest/sdk/netinfo/)) and- AsyncStorage ([RN](https://react-native-async-storage.github.io/async-storage/docs/install) | [Expo](https://docs.expo.dev/versions/v42.0.0/sdk/async-storage/)).···dataKey: 'graphcache-data', // The AsyncStorage key used for the data (defaults to graphcache-data)metadataKey: 'graphcache-metadata', // The AsyncStorage key used for the metadata (defaults to graphcache-metadata)
···+Before installing the [library](https://github.com/urql-graphql/urql/tree/main/packages/storage-rn), ensure you have installed the necessary peer dependencies:- NetInfo ([RN](https://github.com/react-native-netinfo/react-native-netinfo) | [Expo](https://docs.expo.dev/versions/latest/sdk/netinfo/)) and- AsyncStorage ([RN](https://react-native-async-storage.github.io/async-storage/docs/install) | [Expo](https://docs.expo.dev/versions/v42.0.0/sdk/async-storage/)).···dataKey: 'graphcache-data', // The AsyncStorage key used for the data (defaults to graphcache-data)metadataKey: 'graphcache-metadata', // The AsyncStorage key used for the metadata (defaults to graphcache-metadata)
+12
-21
exchanges/auth/README.md
+12
-21
exchanges/auth/README.md
···<p align="center"><strong>An exchange for managing authentication in <code>urql</code></strong></p>-`@urql/exchange-auth` is an exchange for the [`urql`](https://github.com/FormidableLabs/urql) GraphQL client which helps handle auth headers and token refresh·········// check if the error was an auth error (this can be implemented in various ways, e.g. 401 or a special error code)···
···<p align="center"><strong>An exchange for managing authentication in <code>urql</code></strong></p>+`@urql/exchange-auth` is an exchange for the [`urql`](https://github.com/urql-graphql/urql) GraphQL client which helps handle auth headers and token refresh·········// check if the error was an auth error (this can be implemented in various ways, e.g. 401 or a special error code)···
+3
-3
exchanges/auth/package.json
+3
-3
exchanges/auth/package.json
······
······
+3
-3
exchanges/context/README.md
+3
-3
exchanges/context/README.md
···<p align="center"><strong>An exchange for setting operation context in <code>urql</code></strong></p>-`@urql/exchange-context` is an exchange for the [`urql`](https://github.com/FormidableLabs/urql) GraphQL client which can set the operation context both synchronously as well as asynchronously···
···<p align="center"><strong>An exchange for setting operation context in <code>urql</code></strong></p>+`@urql/exchange-context` is an exchange for the [`urql`](https://github.com/urql-graphql/urql) GraphQL client which can set the operation context both synchronously as well as asynchronously···
+3
-3
exchanges/context/package.json
+3
-3
exchanges/context/package.json
···
···
+1
-1
exchanges/execute/README.md
+1
-1
exchanges/execute/README.md
···<p align="center"><strong>An exchange for executing queries against a local schema in <code>urql</code></strong></p>-`@urql/exchange-execute` is an exchange for the [`urql`](https://github.com/FormidableLabs/urql) GraphQL client which executes queries against a local schema.This is a replacement for the default _fetchExchange_ which sends queries over HTTP/S to be executed remotely.
···<p align="center"><strong>An exchange for executing queries against a local schema in <code>urql</code></strong></p>+`@urql/exchange-execute` is an exchange for the [`urql`](https://github.com/urql-graphql/urql) GraphQL client which executes queries against a local schema.This is a replacement for the default _fetchExchange_ which sends queries over HTTP/S to be executed remotely.
+3
-3
exchanges/execute/package.json
+3
-3
exchanges/execute/package.json
······
······
+3
-3
exchanges/multipart-fetch/package.json
+3
-3
exchanges/multipart-fetch/package.json
···"description": "An exchange that allows regular fetch and will transition to multipart when files are included",
···"description": "An exchange that allows regular fetch and will transition to multipart when files are included",
+3
-3
exchanges/persisted-fetch/package.json
+3
-3
exchanges/persisted-fetch/package.json
···
···
+3
-3
exchanges/populate/package.json
+3
-3
exchanges/populate/package.json
···
···
+3
-3
exchanges/refocus/package.json
+3
-3
exchanges/refocus/package.json
···
···
+3
-3
exchanges/request-policy/package.json
+3
-3
exchanges/request-policy/package.json
···
···
+3
-3
exchanges/retry/package.json
+3
-3
exchanges/retry/package.json
···
···
+3
-3
packages/core/package.json
+3
-3
packages/core/package.json
···
···
+4
-4
packages/introspection/package.json
+4
-4
packages/introspection/package.json
···
···
+9
-9
packages/next-urql/README.md
+9
-9
packages/next-urql/README.md
···-<img alt="Test Status" src="https://api.travis-ci.com/FormidableLabs/next-urql.svg?branch=master" />···-`react-is` helps to support server-side `Suspense` with `react-ssr-prepass`. This assumes you have followed the basic installation steps for `urql` [here](https://github.com/FormidableLabs/urql#installation).···
······+`react-is` helps to support server-side `Suspense` with `react-ssr-prepass`. This assumes you have followed the basic installation steps for `urql` [here](https://github.com/urql-graphql/urql#installation).···
+2
-2
packages/next-urql/package.json
+2
-2
packages/next-urql/package.json
···
···
+3
-3
packages/preact-urql/package.json
+3
-3
packages/preact-urql/package.json
···
···
+3
-3
packages/react-urql/package.json
+3
-3
packages/react-urql/package.json
···
···
+2
-1
packages/site/CHANGELOG.md
+2
-1
packages/site/CHANGELOG.md
···-- **Goodbye IE11!** 👋 This major release removes support for IE11. All code that is shipped will be transpiled much less and will _not_ be ES5-compatible anymore, by [@kitten](https://github.com/kitten) (See [#2504](https://github.com/FormidableLabs/urql/pull/2504))
···+- **Goodbye IE11!** 👋 This major release removes support for IE11. All code that is shipped will be transpiled much less and will _not_ be ES5-compatible anymore, by [@kitten](https://github.com/kitten) (See [#2504](https://github.com/urql-graphql/urql/pull/2504))
+3
-3
packages/storage-rn/package.json
+3
-3
packages/storage-rn/package.json
···
···
+4
-4
packages/storybook-addon/package.json
+4
-4
packages/storybook-addon/package.json
···
···
+3
-3
packages/svelte-urql/package.json
+3
-3
packages/svelte-urql/package.json
···
···
+3
-3
packages/vue-urql/package.json
+3
-3
packages/vue-urql/package.json
···
···