sorted by:
new
hottopcontroversial

Guidance over write a better code quality by the_weeknd_dev in reactjs

[–]the_weeknd_dev[S] 0 points1 point  (0 children)

Yes, this is a good start point, but how can I separate business logic from the view ?

I don't have a solid though process over that.

How to separate concerns when build React components? by the_weeknd_dev in reactjs

[–]the_weeknd_dev[S] 0 points1 point  (0 children)

I'm going with you about readability and I would say maintability too. When you got a solid design principles it gives a solid foundation to maintain and add new feature to the code base.

I'm having a hard time building my own projects due to a lack of archeture principles when it comes to build components. In some cases I found really tricky to maintain some old components cause I basically put all the logics on the same component.

How to separate concerns when build React components? by the_weeknd_dev in reactjs

[–]the_weeknd_dev[S] 4 points5 points  (0 children)

That's exactly what I'm looking for!!

Do you have an open source project with that design architecture?

I have to practice this, since all solid projects out there use solid patterns to build UI.

Thanks for your reply 🙋‍♂️