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(core): add back cacheOutcome #3464

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

JoviDeCroock
Copy link
Collaborator

@JoviDeCroock JoviDeCroock commented Dec 13, 2023

Resolves #3462

Summary

In the document cache we put the cache-outcome behind a dev-flag, which is inconsistent as we rely on it in other exchanges and it's not behind a flag in our normalized and ssr cache.

Copy link

changeset-bot bot commented Dec 13, 2023

🦋 Changeset detected

Latest commit: b3c39c1

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

This PR includes changesets to release 1 package
Name Type
@urql/core 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 merged commit 93d7256 into urql-graphql:main Jan 17, 2024
13 checks passed
@github-actions github-actions bot mentioned this pull request Jan 17, 2024
@kitten
Copy link
Member

kitten commented Feb 18, 2024

Just noting down a TODO here for myself since I forgot (@kitten). This should be reimplemented without relying on internal flags being set by other exchanges

@JoviDeCroock JoviDeCroock deleted the add-cache-outcome branch March 4, 2024 18:51
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.

request-policy-exchange behavior differs between dev & production
2 participants