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

Translate "special-props" #95

Merged
merged 2 commits into from Oct 9, 2019
Merged
Changes from all 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
6 changes: 3 additions & 3 deletions content/warnings/special-props.md
@@ -1,9 +1,9 @@
---
title: Special Props Warning
title: Special Props Warnung
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.
Die meisten Attribute bei JSX Elementen werden zur Komponente weitergegeben, allerdings gibt es zwei spezielle Attribute (`ref` und `key`), welche von React genutzt und daher nicht zur Komponente weitergegeben werden.

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.
Versuchst du beispielsweise `this.props.key` innerhalb einer Komponente zu nutzen (z.B. in der `render` Funktion oder in den [propTypes](/docs/typechecking-with-proptypes.html#proptypes)), ist dieses Feld nicht definiert. Wenn du diesen Wert an eine Subkomponente weitergeben möchtest, nutze ein anderes Attribut (bspw. `<ListItemWrapper key={result.id} id={result.id} />`). Auch wenn es redundant scheint, ist es wichtig die Anwendungs- von der Darstellungslogik zu trennen.