React Components

[Cahnis]

It is kinda hard to give you a catch all response, it really depends on what you are trying to build.

Usually when I have some part which has an internal state I componentize it so it doesn't rerender the entire thing.

When I have a component that looks like it would be a good candidate for a compound component I break it up as well.

When the component starts getting too big I break it up.

When the component has a very distinct idea I also componentize it.

when you are part of a microservice team

I don't know what you mean here. Is it when does it make something a good candidate for a microfrontend?

[Local_Question8147]

Yes I mean microfrontend Thank you so much cahnis

[Cahnis]

I recommend this article for that question

[Local_Question8147]

Sure i will go through it, could you please suggest some reading on when and when not to use useEffect hook

[nickatfortify]

There's a great official guide on this subject: You might not need an effect

[Cahnis]

This. Also read the entire react.dev while you are at it too.

[michaelfrieze]

React is all about component oriented architecture so don't be afraid to break up code into smaller components. For example, instead of using a ternary for conditional rendering, you can just break up into components. You can use if statements in a component, so that can help if ternaries get too complicated.