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

Clarify that the result of readQuery should not be modified #4815

Merged
merged 2 commits into from
May 20, 2019

Conversation

dobesv
Copy link
Contributor

@dobesv dobesv commented May 14, 2019

The readQuery call may return an object that is shared with the current contents of cache, which can cause some weird behavior if you mutate the readQuery result.

The `readQuery` call may return an object that is shared with the current contents of cache, which can cause some weird behavior if you mutate the `readQuery` result.
@dobesv
Copy link
Contributor Author

dobesv commented May 14, 2019

This will hopefully help avoid issues like #4760

@benjamn benjamn added this to the Release 2.6.0 milestone May 20, 2019
Copy link
Member

@benjamn benjamn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dobesv!

@benjamn benjamn merged commit b1cf815 into apollographql:master May 20, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants