Proofread Passing Props to a Component - #5129
Conversation
Size ChangesDetails📦 Next.js Bundle AnalysisThis analysis was generated by the next.js bundle analysis action 🤖 This PR introduced no changes to the javascript bundle 🙌 |
| ## Familiar-looking props {/*familiar-props*/} | ||
|
|
||
| Props are the information that you pass to a JSX tag. For example, `className`, `src`, `alt`, `width`, and `height` are some of the props you can pass to an `<img>`: | ||
| Props are the information that you pass to a React element. For example, `className`, `src`, `alt`, `width`, and `height` are some of the props you can pass to an `img` element: |
There was a problem hiding this comment.
We're deemphasizing the concept of "elements" in the new docs. They're kind of fading into background a bit as an implementation detail. E.g. JSX transform doesn't even call createElement. We want to discourage their introspection too. So I'm not sure we'd like to rely on this terminology.
There was a problem hiding this comment.
Can I see a draft of the new terminology somewhere? As element, tag, and attribute are HTML/XML terminology, I'd expect them to be used with JSX and React as well, regardless of the implementation choices. I currently think of tags and attributes as markup syntax and of elements as component instances. Then, props (encompassing children and lacking key) are what the component instance receives. Am I far off?
3 participants
No description provided.