amirho/react.dev
1
0
Fork 0
mirror of https://github.com/reactjs/react.dev.git synced 2026-02-23 20:23:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Note about special props in PropTypes typechecking

Browse Source
This commit is contained in:
Ran Yitzhaki
2018-02-01 21:52:43 +02:00
committed by GitHub
parent 91ac3d8113
commit 423a248c50
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
content/warnings/special-props.md
View File

@@ -6,4 +6,17 @@ permalink: warnings/special-props.html
Most props on a JSX element are passed on to the component, however, there are two special props (`ref` and `key`) which are used by React, and are thus not forwarded to the component.
For instance, attempting to access `this.props.key` from a component (eg. the render function) is not defined. If you need to access the same value within the child component, you should pass it as a different prop (ex: `<ListItemWrapper key={result.id} id={result.id} />`). While this may seem redundant, it's important to separate app logic from reconciling hints.
For instance, attempting to access `this.props.key` from a component (eg. the render function) is not defined. If you need to access the same value within the child component, you should pass it as a different prop (ex: `<ListItemWrapper key={result.id} id={result.id} />`). While this may seem redundant, it's important to separate app logic from reconciling hints.
> Note:
>
> There is no need to validate special props using [PropTypes typechecking](https://reactjs.org/docs/typechecking-with-proptypes.html#proptypes).
>
> By defining `key` or `ref` PropTypes, React will try to access them during props validation phase in the development build.
>
> ```js
> ListItemWrapper.propTypes = {
> id: PropTypes.string,
> key: PropTypes.string // WARNING
> }
> ```