Do you create component for them?
Do you keep them in components folder
Or in separate folder?
Do you provide good types for them?
For further actions, you may consider blocking this person and/or reporting abuse
Read next
ContextCheck: An open-source framework for testing and evaluating LLMs, RAGs, Chatbots
Edwin Lisowski -
Patterns of Enterprise Application Architecture-Day 2
DevByJESUS -
Insecure Direct Object References (IDOR) in Laravel
Pentest Testing Corp -
HackerRank Problem#13
Sunnat Qayumov -
Top comments (3)
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.
Hi!
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.