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

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

merged 3 commits into from Mar 20, 2019

Conversation

seognil
Copy link
Contributor

@seognil seognil commented Feb 17, 2019

@seognil seognil changed the title docs(cn): content/warnings/special-props.md into Chinese docs(cn): translate content/warnings/special-props.md into Chinese Feb 17, 2019
@netlify
Copy link

netlify bot commented Feb 17, 2019

Deploy preview for cn-reactjs ready!

Built with commit 6cd9432

https://deploy-preview-112--cn-reactjs.netlify.com

@seognil seognil mentioned this pull request Feb 17, 2019
@QC-L QC-L added the Pending Review 已翻译,待校对阶段 label Feb 17, 2019
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 所使用,因此不会被传入给组件。
Copy link
Collaborator

Choose a reason for hiding this comment

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

大部分 JSX 元素上的 props 都传递给组件。但 React 占用了两个特殊的 props,refkey,所以不会被传递给组件。

Copy link
Collaborator

Choose a reason for hiding this comment

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

传入给我觉得可以改成【传递给】这样更通顺一些,你觉得呢?

Copy link
Contributor Author

@seognil seognil Feb 19, 2019

Choose a reason for hiding this comment

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

「传入」?
(考虑到 隐含了一个方向的信息)


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

Choose a reason for hiding this comment

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

举个例子,在组件中试图读取 this.props.key (比如通过 render 函数或 propTypes))将得到 undefined. 如果你需要在子组件中获取相同的值,你应该用一个不同的 prop 传入这个值(例如:<ListItemWrapper key={result.id} id={result.id} />)。这看似是多余的,但是将应用程序逻辑和协调提示(reconciliation hint)分开是很重要的。

Copy link
Collaborator

Choose a reason for hiding this comment

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

  1. 未定义用 undefined 表达会不会更清晰一些?
  2. reconciliation hint 是 react 的协调算法中用到的协调提示,这里建议把原文带上

@QC-L QC-L requested a review from sang4lv March 20, 2019 06:51
@QC-L QC-L merged commit 3fa2000 into reactjs:master Mar 20, 2019
OhIAmFine pushed a commit to OhIAmFine/zh-hans.reactjs.org that referenced this pull request May 6, 2019
@awxiaoxian2020 awxiaoxian2020 removed the Pending Review 已翻译,待校对阶段 label Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants