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

(suspense) - Fix suspenseExchange affecting subscriptions and add deprecation note #789

Merged
merged 2 commits into from
May 5, 2020

Conversation

kitten
Copy link
Member

@kitten kitten commented May 3, 2020

NOTE: This doesn't affect server-side / SSR support! It's only for the suspenseExchange of the @urql/exchange-suspense package

This adds a fix that would affect subscription operations, although they remain untouched by suspense-mode.
It also adds a deprecation note, since client-side suspense in urql isn't as stable as it should be and overall not very useful.

This PR will remain opened for discussion briefly, if anyone has good arguments as to why this package shouldn't be deprecated.

kitten added 2 commits May 3, 2020 23:41
Subscription Operations are never subject to suspense-mode.
@kitten kitten added bug 🐛 Oh no! A bug or unintented behaviour. discussion 👥 labels May 3, 2020
@changeset-bot
Copy link

changeset-bot bot commented May 3, 2020

🦋 Changeset is good to go

Latest commit: 4ca6faa

We got this.

This PR includes changesets to release 1 package
Name Type
@urql/exchange-suspense Minor

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

@micabe
Copy link

micabe commented May 4, 2020

Hi all, I confirm my problem disappeared with the sandbox build of suspense exchange.
Applause to @kitten !

@kitten kitten merged commit bde241f into master May 5, 2020
@kitten kitten deleted the fix/suspense-exchange-subscriptions branch May 5, 2020 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Oh no! A bug or unintented behaviour.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants