Best Practice: How I structure my React/ Redux projects

  • But when developing larger projects one have to think about a good structure of components and code artifacts.
  • When it comes to sharing components and (redux-)logic between several project a good composition is keen.
  • The initial project structure created by React Create App looks as follows: – – When you start introducing Redux you also need places for the typical redux artifacts: the store, reducers, epics and actions.
  • contains the reducers which may change the store’s state based on the actions of this component: { } ; { } ; ({ value , output Enter your name and press submit! })
  • For this reason my components always also include a set of actions, epics and reducers: – – includes a plain react component which is wrapped by within : – – These component redux structures may also be with multiple levels, just like the usual ones mentioned above.

When developing frontends I personally love to work with React and Redux due to its functional paradigms: You can easily develop, compose and test web components – Wondeful. But when developing larger projects one have to think about a good structure of components and code artifacts. When it comes to sharing components and (redux-)logic between several project a good composition is keen.
Continue reading “Best Practice: How I structure my React/ Redux projects”