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

(core) - Fix Client hang on promisified sources #1634

Merged
merged 1 commit into from
May 12, 2021

Conversation

kitten
Copy link
Member

@kitten kitten commented May 11, 2021

Resolves #1633

Summary

This will need further investigation and I'd like to find a nicer implementation for this behaviour (our test suite should guide us there).

The short story here is that it seems that the toPromise implementation in Wonka is a little flawed and doesn't quite operate correctly. In fact, it doesn't seem to work correctly as soon as a subject is added to the direct descendants of the source.

Set of changes

  • Replace subject in client.executeRequestOperation with make i.e. anonymous source

@kitten kitten requested a review from JoviDeCroock May 11, 2021 23:37
@changeset-bot
Copy link

changeset-bot bot commented May 11, 2021

🦋 Changeset detected

Latest commit: 53b3321

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

@kitten kitten merged commit 2c295df into main May 12, 2021
@kitten kitten deleted the fix/client-topromise-error branch May 12, 2021 09:58
@urql-ci urql-ci mentioned this pull request May 12, 2021
tmaxmax added a commit to FiveIT/eseuri that referenced this pull request May 14, 2021
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.

Queries or mutations hang when using 'cache-first' or 'cache-only' request policies
2 participants