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

Special props translation #28

Merged
merged 8 commits into from
Feb 9, 2019
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/warnings/special-props.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,6 @@ layout: single
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.
A maioria das propriedades de um elemento JSX são passadas no componente. Porém, existem duas propriedades especiais (`ref` e `key`) que são usadas pelo React, e portanto não são passadas para um componente.
andrescalco marked this conversation as resolved.
Show resolved Hide resolved

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.
Por exemplo, ao tentar acessar `this.props.key` de um componente (ex: a função de renderizar ou [propTypes](/docs/typechecking-with-proptypes.html#proptypes)) não é definido. Caso você precise acessar o mesmo valor de dentro de um componente filho, você deve passá-lo como uma propriedade diferente (ex: `<ListItemWrapper key={result.id} id={result.id} />`). Por mais que isso possa parecer redundante, é importante separar a lógica das dicas de reconciliação da aplicação.