Skip to content
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

Update 04-multiple-components.md #7139

Closed
wants to merge 1 commit into from
Closed

Conversation

DDunc
Copy link

@DDunc DDunc commented Jun 28, 2016

Just had a discussion about this on reactiflux, and the use of "component" here to mean potentially both ReactElement and ReactComponent has already caused some confusion about assigning keys to ReactElements within loops. If the word component is intended to be a catch-all term, the glossary should provide explicit guidance on this.

Just had a discussion about this on reactiflux, and the use of "component" here to mean potentially both ReactElement and ReactComponent has already caused some confusion about assigning keys to ReactElements within loops. If the word component is officially a catch-all term, the glossary should provide more guidance about this.
@ghost
Copy link

ghost commented Jun 28, 2016

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks!

@@ -124,7 +124,7 @@ The situation gets more complicated when the children are shuffled around (as in

When React reconciles the keyed children, it will ensure that any child with `key` will be reordered (instead of clobbered) or destroyed (instead of reused).

The `key` should *always* be supplied directly to the components in the array, not to the container HTML child of each component in the array:
The `key` should *always* be supplied directly to the elements or components in the array, not to the container HTML child of each component in the array:
Copy link
Member

Choose a reason for hiding this comment

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

HTML child

That's also pretty wrong and confusingly worded. Want to try to clean the rest of this up as well?

@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@gaearon
Copy link
Collaborator

gaearon commented Oct 23, 2016

Thanks for the PR!

We just released new docs mostly written from scratch. However this means that all old localized content is gone, as new one needs to be written.

We will track this effort in #8063. The goal is to make it easier for people to review localizations so you wouldn't have to wait for the core team, and your PRs would be reviewed much faster.

Sorry, and thank you for your work!

@gaearon gaearon closed this Oct 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants