Skip to content

Mention that key is not a prop in the docs. #5740

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.

Sign up for GitHub

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
dallonf wants to merge 1 commit into from
Closed

Mention that key is not a prop in the docs. #5740

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/docs/04-multiple-components.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,6 +165,8 @@ var MyComponent = React.createClass({
});
```

Note that `key` is not a prop; trying to access `this.props.key` from inside `ListItemWrapper.render` wil be undefined. 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.

You can also key children by passing a ReactFragment object. See [Keyed Fragments](create-fragment.html) for more details.

## Data Flow
Expand Down