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

docs(cn): translate content/warnings/special-props.md into Chinese #112

Merged
merged 3 commits into from Mar 20, 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
6 changes: 3 additions & 3 deletions content/warnings/special-props.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: Special Props Warning
title: 警告:特殊的 props
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 都会被传入组件,然而,有两个特殊的 props `ref` `key`) 已经被 React 所使用,因此不会被传入组件。

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。如果你需要在子组件中获取相同的值,你应该用一个不同的 prop 来传入它(例如:`<ListItemWrapper key={result.id} id={result.id} />`)。虽然这似乎是多余的,但是将应用程序逻辑和协调提示(reconciliation hints)分开是很重要的。