Skip to content

Translate Special Props #59

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

Merged
merged 2 commits into from
Mar 4, 2019
Merged
Changes from all commits
Commits
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
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.
JSX 엘리먼트 대부분의 props는 컴포넌트로 전달되지만 React에서 사용하는 두 개의 특수 props(`ref` `key`)는 컴포넌트로 전달되지 않습니다.

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.
예를 들어, 컴포넌트에서 `this.props.key`render 함수나 [propTypes](/docs/typechecking-with-proptypes.html#proptypes)에서 접근하면 그 값은 `undefined` 입니다. 자식 컴포넌트 내에서 같은 값에 액세스하고 싶다면 다른 프로퍼티로 전달해야 합니다(예시: `<ListItemWrapper key={result.id} id={result.id} />`). 불필요해 보일지 모르지만, 재조정을 위해 사용되는 속성과 앱 로직을 분리하는 것은 중요합니다.