Mirror: The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
Version Packages (#2448)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
authored by
urql-ci
github-actions[bot]
and committed by
GitHub
dbcc7382
2114429b
+43
-42
-5
.changeset/heavy-rabbits-beam.md
-5
.changeset/heavy-rabbits-beam.md
-5
.changeset/moody-brooms-refuse.md
-5
.changeset/moody-brooms-refuse.md
-6
.changeset/spotty-ligers-play.md
-6
.changeset/spotty-ligers-play.md
···
1
-
---
2
-
'@urql/core': minor
3
-
---
4
-
5
-
Add `Accept` header to GraphQL HTTP requests. This complies to the specification but doesn't go as far as sending `Content-Type` which would throw a lot of APIs off. Instead, we'll now be sending an accept header for `application/graphql+json, application/json` to indicate that we comply with the GraphQL over HTTP protocol.
6
-
This also fixes headers merging to allow overriding `Accept` and `Content-Type` regardless of the user options' casing.
-5
.changeset/thin-worms-unite.md
-5
.changeset/thin-worms-unite.md
-5
.changeset/two-masks-draw.md
-5
.changeset/two-masks-draw.md
-11
.changeset/wise-parents-yawn.md
-11
.changeset/wise-parents-yawn.md
···
1
-
---
2
-
'@urql/svelte': major
3
-
---
4
-
5
-
Reimplement Svelte with functional-only API.
6
-
We've gotten plenty of feedback and issues from the Svelte community about our prior
7
-
Svelte bindings. These bindings favoured a Store singleton to read and write to,
8
-
and a separate signal to start an operation.
9
-
Svelte usually however calls for a lot more flexibility, so we're returning the
10
-
API to a functional-only API again that serves to only create stores, which is more
11
-
similar to the original implementation.
+9
exchanges/graphcache/CHANGELOG.md
+9
exchanges/graphcache/CHANGELOG.md
···
1
1
# @urql/exchange-graphcache
2
2
3
+
## 4.4.1
4
+
5
+
### Patch Changes
6
+
7
+
- Switch `isFragmentHeuristicallyMatching()` to always return `true` for writes, so that we give every fragment a chance to be applied and to write to the cache, by [@kitten](https://github.com/kitten) (See [#2455](https://github.com/FormidableLabs/urql/pull/2455))
8
+
- ⚠️ Fix default storage persisting data after `clear()` was called on it, by [@JoviDeCroock](https://github.com/JoviDeCroock) (See [#2458](https://github.com/FormidableLabs/urql/pull/2458))
9
+
- Updated dependencies (See [#2446](https://github.com/FormidableLabs/urql/pull/2446), [#2456](https://github.com/FormidableLabs/urql/pull/2456), and [#2457](https://github.com/FormidableLabs/urql/pull/2457))
10
+
- @urql/core@2.5.0
11
+
3
12
## 4.4.0
4
13
5
14
### Minor Changes
+2
-2
exchanges/graphcache/package.json
+2
-2
exchanges/graphcache/package.json
···
1
1
{
2
2
"name": "@urql/exchange-graphcache",
3
-
"version": "4.4.0",
3
+
"version": "4.4.1",
4
4
"description": "A normalized and configurable cache exchange for urql",
5
5
"sideEffects": false,
6
6
"homepage": "https://formidable.com/open-source/urql/docs/graphcache",
···
65
65
"preset": "../../scripts/jest/preset"
66
66
},
67
67
"dependencies": {
68
-
"@urql/core": ">=2.3.6",
68
+
"@urql/core": ">=2.5.0",
69
69
"wonka": "^4.0.14"
70
70
},
71
71
"peerDependencies": {
+12
packages/core/CHANGELOG.md
+12
packages/core/CHANGELOG.md
···
1
1
# @urql/core
2
2
3
+
## 2.5.0
4
+
5
+
### Minor Changes
6
+
7
+
- Add `Accept` header to GraphQL HTTP requests. This complies to the specification but doesn't go as far as sending `Content-Type` which would throw a lot of APIs off. Instead, we'll now be sending an accept header for `application/graphql+json, application/json` to indicate that we comply with the GraphQL over HTTP protocol.
8
+
This also fixes headers merging to allow overriding `Accept` and `Content-Type` regardless of the user options' casing, by [@kitten](https://github.com/kitten) (See [#2457](https://github.com/FormidableLabs/urql/pull/2457))
9
+
10
+
### Patch Changes
11
+
12
+
- Support aborting in `withPromise` cases, by [@JoviDeCroock](https://github.com/JoviDeCroock) (See [#2446](https://github.com/FormidableLabs/urql/pull/2446))
13
+
- Passthrough responses with content type of `text/*` as error messages, by [@kitten](https://github.com/kitten) (See [#2456](https://github.com/FormidableLabs/urql/pull/2456))
14
+
3
15
## 2.4.4
4
16
5
17
### Patch Changes
+1
-1
packages/core/package.json
+1
-1
packages/core/package.json
+17
packages/svelte-urql/CHANGELOG.md
+17
packages/svelte-urql/CHANGELOG.md
···
1
1
# @urql/svelte
2
2
3
+
## 2.0.0
4
+
5
+
### Major Changes
6
+
7
+
- Reimplement Svelte with functional-only API.
8
+
We've gotten plenty of feedback and issues from the Svelte community about our prior
9
+
Svelte bindings. These bindings favoured a Store singleton to read and write to,
10
+
and a separate signal to start an operation.
11
+
Svelte usually however calls for a lot more flexibility, so we're returning the
12
+
API to a functional-only API again that serves to only create stores, which is more
13
+
similar to the original implementation, by [@jonathanstanley](https://github.com/jonathanstanley) (See [#2370](https://github.com/FormidableLabs/urql/pull/2370))
14
+
15
+
### Patch Changes
16
+
17
+
- Updated dependencies (See [#2446](https://github.com/FormidableLabs/urql/pull/2446), [#2456](https://github.com/FormidableLabs/urql/pull/2456), and [#2457](https://github.com/FormidableLabs/urql/pull/2457))
18
+
- @urql/core@2.5.0
19
+
3
20
## 1.3.3
4
21
5
22
### Patch Changes
+2
-2
packages/svelte-urql/package.json
+2
-2
packages/svelte-urql/package.json
···
1
1
{
2
2
"name": "@urql/svelte",
3
-
"version": "1.3.3",
3
+
"version": "2.0.0",
4
4
"description": "A highly customizable and versatile GraphQL client for Svelte",
5
5
"sideEffects": false,
6
6
"homepage": "https://formidable.com/open-source/urql/docs/",
···
55
55
"svelte": "^3.0.0"
56
56
},
57
57
"dependencies": {
58
-
"@urql/core": "^2.3.6",
58
+
"@urql/core": "^2.5.0",
59
59
"wonka": "^4.0.14"
60
60
},
61
61
"devDependencies": {