Currently, we use one huge useReducer to keep track of the configurator state. Due to this design, the whole application re-renders on every keystroke when adding a chart title, for example (or really, changing any other property).
While it's not terribly slow, the lag is clearly noticeable, especially when developing the application. We should potentially split up the one big reducer into several, dedicated ones that would only make the affected parts of the app re-render.
Currently, we use one huge
useReducerto keep track of the configurator state. Due to this design, the whole application re-renders on every keystroke when adding a chart title, for example (or really, changing any other property).While it's not terribly slow, the lag is clearly noticeable, especially when developing the application. We should potentially split up the one big reducer into several, dedicated ones that would only make the affected parts of the app re-render.