8000 docs remove rootNode for componentDidMount/Update by chenglou · Pull Request #582 · facebook/react · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

docs remove rootNode for componentDidMount/Update #582

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

Closed
wants to merge 1 commit into from
Closed

docs remove rootNode for componentDidMount/Update #582

wants to merge 1 commit into from

Conversation

chenglou
Copy link
Contributor

No description provided.

@vjeux
Copy link
Contributor
vjeux commented Nov 21, 2013

cc @zpao. I'm good with this change but you wanted to mark it as deprecated and really remove it later.

@chenglou
Copy link
Contributor Author

where would be a good place to mark this?

```

Invoked immediately after rendering occurs. At this point in the lifecycle, the component has a DOM representation which you can access via the `rootNode` argument or by calling `this.getDOMNode()`.
Invoked immediately after rendering occurs. At this point in the lifecycle, the component has a DOM representation which you can access via `this.getDOMNode()`.
Copy link
Member

Choose a reason for hiding this comment

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

Let's add a > Note about the previous API here. Since we aren't providing and deprecation notices we should mention it somewhere. Something like we did for http://facebook.github.io/react/docs/top-level-api.html#react.unmountcomponentatnode

@chenglou chenglou closed this Nov 27, 2013
@chenglou chenglou deleted the didMout-didUpdate-new branch November 28, 2013 02:51
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.

3 participants
0