This is an interesting thought. As someone who is also new to React, making almost everything a component makes sense. At the same time, for a small app or project, it could be overboard.
For the first full react project I did, everything event headers was a component but I had requirements I was trying to meet.
See my comment about familiarizing yourself with context. It's a huge help to treat it as second nature to keep shared local state, and will improve the readability of your code by breaking into smaller files even if you don't immediately have a case for code reuse.
@helderburato
's comment about atoms, molecules, organisms and templates is helpful too, even if you don't follow his structure.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is an interesting thought. As someone who is also new to React, making almost everything a component makes sense. At the same time, for a small app or project, it could be overboard.
For the first full react project I did, everything event headers was a component but I had requirements I was trying to meet.
See my comment about familiarizing yourself with context. It's a huge help to treat it as second nature to keep shared local state, and will improve the readability of your code by breaking into smaller files even if you don't immediately have a case for code reuse.
@helderburato 's comment about atoms, molecules, organisms and templates is helpful too, even if you don't follow his structure.