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

Update docs to indicate that componentDDidUpdate is fired after changes are flushed to the DOM. Fix #2801

Merged
merged 1 commit into from
Jan 5, 2015

Conversation

jimfb
Copy link
Contributor

@jimfb jimfb commented Jan 2, 2015

Update docs to indicate that componentDDidUpdate is fired after changes are flushed to the DOM. Fixes #2796

zpao added a commit that referenced this pull request Jan 5, 2015
Update docs to indicate that componentDDidUpdate is fired after changes are flushed to the DOM.  Fix
@zpao zpao merged commit a7028c4 into facebook:master Jan 5, 2015
zpao added a commit that referenced this pull request Jan 17, 2015
Update docs to indicate that componentDDidUpdate is fired after changes are flushed to the DOM.  Fix
zpao added a commit that referenced this pull request Jan 17, 2015
@gnprice
Copy link

gnprice commented Dec 5, 2019

FTR, because later discussion on #2796 expresses confusion about what became of this change: it looks like it was effectively reverted in 2016 in the massive commit 455d2d1 "New Documentation", which reorganized the docs and made tons of editorial changes.

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.

clarify when componentDidUpdate fires.
3 participants