Skip to content
markdown guide

Good question! I'm guessing it depends on your setup and if your building this as part of a team.

On my dev team, we usually break them out into their own file unless it's a styled component just for that parent component.

Currently we keep them in a folder for that specific item. For example, if we had a PanelRenderer that had a specific PanelChilr that only worked for it they would be placed in the PanelRenderer directory.

Even if it's only used once, we prefer to type them fully. This helps with future refactors, bug fixes, additional features.



I won't provide an answer but a thought.

I don't believe there's a reason making some block of code a component if it is not reusable.


Yeah, that a good option but parent components can be huge without extraction.

Classic DEV Post from Feb 24

DISCUSS: Technical Interview Horror Stories

In this week's Ladybug Podcast episode we discussed the frontend technical interview process. Te...

Saurabh Sharma profile image
Web development | #javaScript #css #reactjs