Hi, you just described a MVC pattern for React components.
Daniel Beutner

It’s similar to MVC only in that you break apart your concerns about data, behavior, and presentation. The biggest difference being their is no “model” or “controller” (unless you want to count react-router) and the behavior is not related to that data in most cases, it behavior of the react components. A better way to phrase it may have been separate app data, component state, and presentation of state and data. Also, I didn’t want to use the term “MVC” because that term has a lot of baggage attached to it and I didn’t want to confuse the point I am trying to make. It does feel MVCish in the approach because both patterns promote separation of concerns. Hope that clarifies!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.