Skip to content

Coding Guidelines: Controllable React Components #5301

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.

Sign up for GitHub

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

Open
jamesricky wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Coding Guidelines: Controllable React Components #5301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions docs/docs/9-coding-guidelines/09-react.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,10 @@ sidebar_position: -5
- How to structure folders: "Move files around until it feels right."
Recommendation: separate by modules instead of by type ([File Structure – React](https://legacy.reactjs.org/docs/faq-structure.html#grouping-by-features-or-routes)).

## Reusable, Controllable Components

Reusable components should generally be controllable. Expose props (e.g., `value`, `open`) and change handlers (e.g., `onChange`, `onOpenChange`) so consumers can manage state externally. For application-specific components where reuse is not a concern, managing state internally is perfectly fine.

## Naming

### Casing
Expand Down
Loading