Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump @urql/exchange-graphcache from 5.0.5 to 6.3.3 #2263

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 5, 2023

Bumps @urql/exchange-graphcache from 5.0.5 to 6.3.3.

Release notes

Sourced from @​urql/exchange-graphcache's releases.

@​urql/exchange-graphcache@​6.3.3

Patch Changes

  • ⚠️ Fix a typo that caused an inverted condition, for checking owned data, to cause incorrect results when handling null values and encountering them first Submitted by @​kitten (See #3371)

@​urql/exchange-graphcache@​6.3.2

Patch Changes

  • ⚠️ Fix extra variables in mutation results regressing by a change made in #3317. The original operation wasn't being preserved anymore Submitted by @​kitten (See #3356)

@​urql/exchange-graphcache@​6.3.1

Patch Changes

  • Reset partial result marker when reading from selections when a child value sees a cache miss. This only affects resolvers on child values enabling info.partial while a parent may abort early instead Submitted by @​kitten (See #3340)
  • ⚠️ Fix @_optional directive not setting info.partial = true on cache miss and fix usage of info.parentKey and info.parentFieldKey usage in default directives Submitted by @​kitten (See #3338)
  • Replace implementation for @_optional and @_required with built-in handling inside cache reads to allow @_optional to work for nested selection sets Submitted by @​kitten (See #3341)

@​urql/exchange-graphcache@​6.3.0

Minor Changes

  • Allow scalar values on the parent to be accessed from parent[info.fieldName] consistently. Prior to this change parent[fieldAlias] would get populated, which wouldn’t always result in a field that’s consistently accessible Submitted by @​kitten (See #3336)
  • Allow cache.resolve to return undefined when a value is not cached to make it easier to cause a cache miss in resolvers. Reminder: Returning undefined from a resolver means a field is uncached, while returning null means that a field’s value is null without causing a cache miss Submitted by @​kitten (See #3333)

Patch Changes

  • Record a dependency when __typename field is read. This removes a prior, outdated exception to avoid confusion when using cache.resolve(entity, '__typename') which doesn't cause the cache to record a dependency Submitted by @​kitten (See #3335)
  • ⚠️ Fix cases where ResolveInfo’s parentFieldKey was incorrectly populated with a key that isn’t a field key (allowing for cache.resolve(info.parentKey, info.parentFieldKey) to be possible) but was instead set to info.parentKey combined with the field key Submitted by @​kitten (See #3336)

@​urql/exchange-graphcache@​6.2.0

Minor Changes

  • Implement local directives. It’s now possible to add client-only directives to queries by adding them to the cacheExchange’s new directives option. Directives accept an object of their arguments and return a resolver. When a field is annotated with a resolver, e.g. @_optional or @_required, their resolvers from the directives config are executed. This means it’s now possible to use @_relayPagination for example, by passing adding the relayPagination helper to the config. Due to the change in #3317, any directive in queries that’s prefixed with an underscore (_) is only visible to Graphcache and not the API. Submitted by undefined (See urql-graphql/urql#3306)

Patch Changes

... (truncated)

Changelog

Sourced from @​urql/exchange-graphcache's changelog.

6.3.3

Patch Changes

  • ⚠️ Fix a typo that caused an inverted condition, for checking owned data, to cause incorrect results when handling null values and encountering them first Submitted by @​kitten (See #3371)

6.3.2

Patch Changes

  • ⚠️ Fix extra variables in mutation results regressing by a change made in #3317. The original operation wasn't being preserved anymore Submitted by @​kitten (See #3356)

6.3.1

Patch Changes

  • Reset partial result marker when reading from selections when a child value sees a cache miss. This only affects resolvers on child values enabling info.partial while a parent may abort early instead Submitted by @​kitten (See #3340)
  • ⚠️ Fix @_optional directive not setting info.partial = true on cache miss and fix usage of info.parentKey and info.parentFieldKey usage in default directives Submitted by @​kitten (See #3338)
  • Replace implementation for @_optional and @_required with built-in handling inside cache reads to allow @_optional to work for nested selection sets Submitted by @​kitten (See #3341)

6.3.0

Minor Changes

  • Allow scalar values on the parent to be accessed from parent[info.fieldName] consistently. Prior to this change parent[fieldAlias] would get populated, which wouldn’t always result in a field that’s consistently accessible Submitted by @​kitten (See #3336)
  • Allow cache.resolve to return undefined when a value is not cached to make it easier to cause a cache miss in resolvers. Reminder: Returning undefined from a resolver means a field is uncached, while returning null means that a field’s value is null without causing a cache miss Submitted by @​kitten (See #3333)

Patch Changes

  • Record a dependency when __typename field is read. This removes a prior, outdated exception to avoid confusion when using cache.resolve(entity, '__typename') which doesn't cause the cache to record a dependency Submitted by @​kitten (See #3335)
  • ⚠️ Fix cases where ResolveInfo’s parentFieldKey was incorrectly populated with a key that isn’t a field key (allowing for cache.resolve(info.parentKey, info.parentFieldKey) to be possible) but was instead set to info.parentKey combined with the field key Submitted by @​kitten (See #3336)

6.2.0

Minor Changes

  • Implement local directives. It’s now possible to add client-only directives to queries by adding them to the cacheExchange’s new directives option. Directives accept an object of their arguments and return a resolver. When a field is annotated with a resolver, e.g. @_optional or @_required, their resolvers from the directives config are executed. This means it’s now possible to use @_relayPagination for example, by passing adding the relayPagination helper to the config.

... (truncated)

Commits
  • 6564951 Version Packages (#3372)
  • 022c7d2 fix(graphcache): Fix typo in owned data null resolution for resolvers (#3371)
  • 6431511 fix(core): Force client.reexecuteOperation to dispatch (#3363)
  • d175d48 Version Packages (#3357)
  • ddbc3dc fix(graphcache): Fix extra variables regression (#3356)
  • 344b544 chore(workspace): Update eslint and add missing rules (#3350)
  • 743e5b4 Version Packages (#3339)
  • 438d75f fix(graphcache): Replace default optional/required directive implementation (...
  • 25a34c6 fix(graphcache): Fix info.partial edge case for @_optional (#3340)
  • 51f72c2 fix(graphcache): Fix partial and info usage in default directives (#3338)
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [@urql/exchange-graphcache](https://github.com/urql-graphql/urql/tree/HEAD/exchanges/graphcache) from 5.0.5 to 6.3.3.
- [Release notes](https://github.com/urql-graphql/urql/releases)
- [Changelog](https://github.com/urql-graphql/urql/blob/main/exchanges/graphcache/CHANGELOG.md)
- [Commits](https://github.com/urql-graphql/urql/commits/@urql/[email protected]/exchanges/graphcache)

---
updated-dependencies:
- dependency-name: "@urql/exchange-graphcache"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the react label Sep 5, 2023
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Sep 5, 2023

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8252a30
Status: ✅  Deploy successful!
Preview URL: https://5418dfcd.kitsu-web.pages.dev
Branch Preview URL: https://dependabot-npm-and-yarn-reac-31b8.kitsu-web.pages.dev

View logs

@NuckChorris
Copy link
Member

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 6, 2023

Looks like @urql/exchange-graphcache is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Nov 6, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/react/urql/exchange-graphcache-6.3.3 branch November 6, 2023 03:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant