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

fix(graphcache): case where a mutation would also be counted in the loop-protection #2761

Merged
merged 3 commits into from
Oct 25, 2022

Conversation

JoviDeCroock
Copy link
Collaborator

Summary

Currently we initiate loop protection for all operations, this should actually only happen for queries reexecuting one another

@changeset-bot
Copy link

changeset-bot bot commented Oct 24, 2022

🦋 Changeset detected

Latest commit: b5769ff

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@urql/exchange-graphcache Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@JoviDeCroock JoviDeCroock marked this pull request as ready for review October 25, 2022 10:40
@JoviDeCroock JoviDeCroock requested a review from kitten October 25, 2022 10:42
@JoviDeCroock JoviDeCroock merged commit 15482d8 into main Oct 25, 2022
@JoviDeCroock JoviDeCroock deleted the try-fix branch October 25, 2022 11:13
@urql-ci urql-ci mentioned this pull request Oct 25, 2022
xuanduc987 added a commit to xuanduc987/urql that referenced this pull request Sep 9, 2024
…uting operations become the same set

The PR urql-graphql#2761 moved `reexecutingOperations = dependentOperations` assignment
into `if (operation.kind === 'query')` guard. Thus after a completion of
mutation, `dependentOperations = _reexecutingOperations` make reexecuting and
dependent operations the same set object.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants