reactjs - React.js : The difference between findDOMNode and getDOMNode

Question

谁能告诉我两者有什么区别

React.findDOMNode(this.refs.email).value

和

this.refs.email.getDOMNode().value

他们在做同样的事情 - 获取元素的值，但是我应该在哪里使用哪个。

Answer 1

component.getDOMNode() 从 React 0.13 开始已弃用:

Added new top-level API React.findDOMNode(component), which should be used in place of component.getDOMNode(). The base class for ES6-based components will not have getDOMNode. This change will enable some more patterns moving forward.

通过 http://facebook.github.io/react/blog/2015/03/10/react-v0.13.html#new-features

它可能会在 React 的 future 版本中被删除(但不要引用我的话，因为我找不到好的引用资料)。

<小时/>

编辑:更新以反射(reflect) React 0.14

getDOMNode() 在 0.13 和 0.14 中抛出警告，它将在 0.15 中完全删除:

With each returned DOM node, we've added a getDOMNode method for backwards compatibility that will work with a warning until 0.15.

通过 https://facebook.github.io/react/blog/2015/10/07/react-v0.14.html#new-deprecations-introduced-with-a-warning

另请注意，从 0.14 开始，React DOM 组件不再需要调用 findDOMNode 或 getDOMNode:

The other big change we’re making in this release is exposing refs to DOM components as the DOM node itself. That means: we looked at what you can do with a ref to a React DOM component and realized that the only useful thing you can do with it is call this.refs.giraffe.getDOMNode() to get the underlying DOM node. Starting with this release, this.refs.giraffe is the actual DOM node. Note that refs to custom (user-defined) components work exactly as before; only the built-in DOM components are affected by this change.

通过 https://facebook.github.io/react/blog/2015/10/07/react-v0.14.html#dom-node-refs

<小时/>

来自 GitHub 上 React 存储库的相关代码和提交:

• https://github.com/facebook/react/blob/a6d03f36a4a9e7c1e6688bdba89656f2e20e7df8/src/modern/class/ReactComponent.js#L101-L104
• https://github.com/facebook/react/commit/b46a6ce4bb8d6087ed424764f41fe4b8e248b3b4
• https://github.com/facebook/react/commit/fb23276178b28fdcb75aa22be013a91755f7ad0a