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

explained why need to re-call .find() after update #2140

Merged
merged 1 commit into from May 29, 2019
Merged

explained why need to re-call .find() after update #2140

merged 1 commit into from May 29, 2019

Conversation

skyboyer
Copy link
Contributor

@skyboyer skyboyer commented May 25, 2019

This behavior currently is explained only in 2-to-3 version migration guide. People who never used v2 have small chance to get there.
Since it's related to different methods and both mount/shallow suppose this file is better place for describing that.

Closes #2139.

This behavior currently is explained only in 2-to-3 version migration guide. People who never used v2 have small chance to get there.
Since it's related to different methods and both mount/shallow suppose this file is better place for describing that.
docs/common-issues.md Outdated Show resolved Hide resolved
@ljharb ljharb added the docs label May 26, 2019
@ljharb ljharb merged commit d824527 into enzymejs:master May 29, 2019
@skyboyer skyboyer deleted the patch-1 branch May 29, 2019 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

cached find() result is not updated after re-render
2 participants