+1 -1

docs/api/core.md

reviewed

··· 176 176 | context | `OperationContext` | Additional metadata passed to exchange. | 177 177 178 178 > **Note:** In `urql` the `operationName` on the `Operation` isn't the actual name of an operation 179 179 - > and dervied from the GraphQL `DocumentNode`, but instead a type of operation, like `'query'` or 179 179 + > and derived from the GraphQL `DocumentNode`, but instead a type of operation, like `'query'` or 180 180 > `'teardown'` 181 181 182 182 ### RequestPolicy

+2 -2

docs/api/graphcache.md

reviewed

··· 153 153 | ------------- | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 154 154 | writeData | `(delta: SerializedEntries) => Promise<void>` | This provided method must be able to accept an object of key-value entries that will be persisted to the storage. This method is called as a batch of updated entries becomes ready. | 155 155 | readData | `() => Promise<SerializedEntries>` | This provided method must be able to return a single combined object of previous key-value entries that have been previously preserved using `writeData`. It's only called on startup. | 156 156 - | writeMetadata | `(json: SerializedRequest[]) => void` | This provided method must be able to persist metdata for the cache. For backwards compatibility it should be able to accept any JSON data. | 157 157 - | readMetadata | `() => Promise<null | SerializedRequest[]>` | This provided method must be able to read the persisted metdata that has previously been written using `writeMetadata`. It's only called on startup. | 156 156 + | writeMetadata | `(json: SerializedRequest[]) => void` | This provided method must be able to persist metadata for the cache. For backwards compatibility it should be able to accept any JSON data. | 157 157 + | readMetadata | `() => Promise<null | SerializedRequest[]>` | This provided method must be able to read the persisted metadata that has previously been written using `writeMetadata`. It's only called on startup. | 158 158 | onOnline | `(cb: () => void) => void` | This method must be able to accept a callback that is called when the user's device comes back online. | 159 159 160 160 These options are split into three parts:

+1 -1

docs/concepts/README.md

reviewed

··· 8 8 In this chapter we'll learn about the motivation behind `urql`, the architecture that drives it, the 9 9 inner workings of the `Client`, and how to write extensions and addons, also known as _Exchanges_. 10 10 11 11 - Each page goes a little further in explaning a core concept of `urql`. 11 11 + Each page goes a little further in explaining a core concept of `urql`. 12 12 13 13 - [**Philosophy**](./philosophy.md) gives a quick overview of the different aspects of GraphQL clients and `urql` in 14 14 particular, which shines a light on why you may want to use `urql`.

+1 -1

docs/concepts/core-package.md

reviewed

··· 89 89 90 90 Since the streams in `urql` operate synchronously, internally this method subscribes to 91 91 `client.executeQuery` and unsubscribes immediately. If a result is available in the cache it will be 92 92 - resolved synchronosuly prior to the unsubscribe. If not, the query is cancelled and no request will be sent to the GraphQL API. 92 92 + resolved synchronously prior to the unsubscribe. If not, the query is cancelled and no request will be sent to the GraphQL API. 93 93 94 94 ## Common Utilities in Core 95 95

+1 -1

docs/concepts/stream-patterns.md

reviewed

··· 40 40 asynchronously. 41 41 42 42 Also most Observable libraries come with a toolkit of helper functions that are similar to the 43 43 - methods on arrays, so you're likely to see `map` and `filter` — amongst other utlities — in those 43 43 + methods on arrays, so you're likely to see `map` and `filter` — amongst other utilities — in those 44 44 libraries. 45 45 46 46 Read [this Gist](https://gist.github.com/staltz/868e7e9bc2a7b8c1f754) for a more in-depth

+1 -1

docs/graphcache/README.md

reviewed

··· 66 66 67 67 The package exports the `cacheExchange` which replaces the default `cacheExchange` in `@urql/core`. 68 68 This new `cacheExchange` must be instantiated using some options, which are used to customise 69 69 - _Graphcache_ as introduced in the ["Features" section above.](#features) Howver, you can get started 69 69 + _Graphcache_ as introduced in the ["Features" section above.](#features) However, you can get started 70 70 without passing any options. 71 71 72 72 ```js

+3 -3

docs/graphcache/computed-queries.md

reviewed

··· 83 83 ]; 84 84 ``` 85 85 86 86 - Let's get the `author` for a todo. 86 86 + Lets get the `author` for a todo. 87 87 88 88 ```js 89 89 const parent = { ··· 160 160 > [graphql-tag](https://github.com/apollographql/graphql-tag) because `writeFragment` only accepts 161 161 > GraphQL `DocumentNode`s as inputs, and not strings. 162 162 163 163 - This way we'll get the Todo with id 1 and the relevant data we are askng for in the 163 163 + This way we'll get the Todo with id 1 and the relevant data we are asking for in the 164 164 fragment. 165 165 166 166 ## Pagination ··· 197 197 Given you have a [relay-compatible schema](https://facebook.github.io/relay/graphql/connections.htm) 198 198 on your backend we offer the possibility of endless data resolving. 199 199 This means that when you fetch the next page in your data 200 200 - received in `useQuery` you'll see the previous pages as well. This is usefull for 200 200 + received in `useQuery` you'll see the previous pages as well. This is useful for 201 201 endless scrolling. 202 202 203 203 You can achieve this by importing `relayPagination` from `@urql/exchange-graphcache/extras`.

+3 -3

exchanges/graphcache/CHANGELOG.md

reviewed

··· 23 23 ### Major Changes 24 24 25 25 - Remove the deprecated `populateExchange` export from `@urql/exchange-graphcache`. 26 26 - If you're using the `populateExchange`, please install the seprate `@urql/exchange-populate` package and import it from there, by [@kitten](https://github.com/kitten) (See [#840](https://github.com/FormidableLabs/urql/pull/840)) 26 26 + If you're using the `populateExchange`, please install the separate `@urql/exchange-populate` package and import it from there, by [@kitten](https://github.com/kitten) (See [#840](https://github.com/FormidableLabs/urql/pull/840)) 27 27 - The deprecated `cache.invalidateQuery()` method has been removed. Please migrate over to `cache.invalidate()` instead, which operates on individual fields instead of queries, by [@kitten](https://github.com/kitten) (See [#840](https://github.com/FormidableLabs/urql/pull/840)) 28 28 29 29 ### Minor Changes ··· 295 295 then you now need to use `inspectFields` and `resolveFieldByKey` instead. You may also now make 296 296 use of `cache.keyOfField`. (More info on [#128](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/128)) 297 297 298 298 - - ✨ Implement `populateExchange` (eee [#120](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/120)) 298 298 + - ✨ Implement `populateExchange` (see [#120](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/120)) 299 299 - Improve type safety of `invariant` and `warning` (see [#121](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/121)) 300 300 - Reduce size of `populateExchange` (see [#122](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/122)) 301 301 - Move more code to KVMap (see [#125](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/125)) ··· 352 352 353 353 - Trims down the size by 100 bytes (see [#96](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/96)) 354 354 - Include the `/extras` build in the published version (see [#97](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/97)) 355 355 - - Invariant and warnings will now have an error code associated with a more elabore explanation (see [#99](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/99)) 355 355 + - Invariant and warnings will now have an error code associated with a more elaborate explanation (see [#99](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/99)) 356 356 - Invariant errors will now be included in your production bundle (see [#100](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/100)) 357 357 - Fixes the relayPagination helper to correctly return partial results (see [#101](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/101)) 358 358 - Add special case to relayPagination for first and last during inwards merge (see [#102](https://github.com/FormidableLabs/urql-exchange-graphcache/pull/102))

+1 -1

exchanges/suspense/README.md

reviewed

··· 116 116 ### Usage with `ssrExchange` 117 117 118 118 If you're also using the `ssrExchange` for server-side rendered data, you will have to use 119 119 - an additonal flag to indicate to it when it's running on the server-side and when it's running 119 119 + an additional flag to indicate to it when it's running on the server-side and when it's running 120 120 on the client-side. 121 121 122 122 By default, the `ssrExchange` will look at `client.suspense`. If the `urql` Client is in suspense

+2 -2

packages/next-urql/CHANGELOG.md

reviewed

··· 40 40 41 41 The second argument may now be used to pass `{ ssr: true }` explicitly, when you are 42 42 wrapping a page without another `getInitialProps` method. This gives you better support 43 43 - when you're implement custom methods like `getStaticProps`. 43 43 + when you implement custom methods like `getStaticProps`. 44 44 45 45 ### Major Changes 46 46 ··· 197 197 198 198 ## 0.2.1 199 199 200 200 - This release fixes a regression introduced in 0.2.0 involving circular structures created bt `withUrqlClient`'s `getInitialProps` method. 200 200 + This release fixes a regression introduced in 0.2.0 involving circular structures created by `withUrqlClient`'s `getInitialProps` method. 201 201 202 202 ### Fixed 203 203

+1 -1

packages/react-urql/CHANGELOG.md

reviewed

··· 281 281 282 282 ## 1.1.1 283 283 284 284 - This release comes with two small patches. One being a crticial fix, 284 284 + This release comes with two small patches. One being a critical fix, 285 285 where cancelled requests would be erroneously deduped, which meant 286 286 a previously cancelled query would never be fetched. 287 287