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.

Sign up for GitHub

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

Jump to bottom

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

Commits on May 25, 2019

  1. [Docs] explained why need to re-call .find() after update 

    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.
    @skyboyer @ljharb
    skyboyer authored and ljharb committed May 25, 2019
    Copy the full SHA
    d824527 View commit details
    Browse the repository at this point in the history