Skip to content

Conversation

@stubailo
Copy link
Contributor

@stubailo stubailo commented Oct 15, 2016

Opening to keep track of the diff.

glasser and others added 4 commits October 13, 2016 15:46
react-apollo calls setOptions and ignores the return value. Sometimes
setOptions calls this.result() which subscribes and unsubscribes to the
query, but this actually unsubscribes the main subscription too, which
is bad.  We should fix the underlying bug but until then react-apollo
can call _setOptionsNoResult instead.
(this test fails if you use `setVariables`
@stubailo stubailo changed the title 0.4.21 fixes [do not merge] 0.4.21 fixes Oct 15, 2016
@stubailo stubailo modified the milestone: Release 0.5 Oct 16, 2016
@stubailo
Copy link
Contributor Author

Fixed in #791

@stubailo stubailo closed this Oct 17, 2016
@glasser
Copy link
Member

glasser commented Oct 18, 2016

Great. Since we never added the hacky APIs on master, and react-apollo's current release won't pull in apollo-client 0.5.x, all we need to do is wait for apollo-client to come out, change react-apollo to request apollo-client 0.5.x, and revert the use of the hacky API to using the normal version.

@stubailo
Copy link
Contributor Author

@glasser on it!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants