Skip to content

Commit c434be8

Browse files
numb86gaearon
authored andcommitted
Fix broken link. (#861)
1 parent d0cdc9e commit c434be8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/warnings/special-props.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,4 @@ permalink: warnings/special-props.html
66

77
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.
88

9-
For instance, attempting to access `this.props.key` from a component (i.e., the render function or [propTypes](https://reactjs.org/docs/typechecking-with-proptypes.html#proptypes)) 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.
9+
For instance, attempting to access `this.props.key` from a component (i.e., the render function or [propTypes](/docs/typechecking-with-proptypes.html#proptypes)) 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.

0 commit comments

Comments
 (0)