Skip to content

Commit 6bb0d33

Browse files
authored
Clarify language in components-and-props.md (#3020)
* Clarify language in components-and-props.md This is a nit for a few reasons: - The point that extracting a component that "is complex enough on its own" means that it's not necessarily reusable. - Extracting the components listed in the same sentence (e.g. App) are not necessarily reusable. - This ends the section "Extracting Components" with a reference to extraction instead of re-usability. - This delimits extracting into a separate component from creating a re-usable component. * Update components-and-props.md * Update components-and-props.md
1 parent 7aace64 commit 6bb0d33

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/docs/components-and-props.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -233,7 +233,7 @@ function Comment(props) {
233233

234234
[](codepen://components-and-props/extracting-components-continued)
235235

236-
Extracting components might seem like grunt work at first, but having a palette of reusable components pays off in larger apps. A good rule of thumb is that if a part of your UI is used several times (`Button`, `Panel`, `Avatar`), or is complex enough on its own (`App`, `FeedStory`, `Comment`), it is a good candidate to be a reusable component.
236+
Extracting components might seem like grunt work at first, but having a palette of reusable components pays off in larger apps. A good rule of thumb is that if a part of your UI is used several times (`Button`, `Panel`, `Avatar`), or is complex enough on its own (`App`, `FeedStory`, `Comment`), it is a good candidate to be extracted to a separate component.
237237

238238
## Props are Read-Only {#props-are-read-only}
239239

0 commit comments

Comments
 (0)