Earlier quoted context omitted.
That would make it me, I’m surprised people already start noticing the reducer logic in there. Better get the docs out soon :)
Reducers are almost always the first thing I dig into whenever I open up a Redux project. Tells you what the state structure is, how it's being updated, what sorts of actions are being used, etc. Only looked through the code for a few minutes, but a couple things I noticed: - You've got an interesting wrapper around `connect()`, which includes something called `withLocalSelector()`. Can you clarify what that does, an…
- I know nested state has performance drawbacks, that's why we try to flatten certain properties with large arrays, such as datasets, layers, and layer data. But for other properties that are simple strings, floats or boolean, I think it's fine to have them nested. Because we have this reducer plugin feature, where developers can add custom reducer handlers, I try to keep the number of reducer small, so it's easier to explain what they each do. Besides that, I came across couple of cases where 1 action updates multiple reducers sequentially, I don't want to add thunk, so we then had to add this composer function which is kinda complex.
There are lots of questions, don't have time to answer them all, but I would love to keep this conversation going. :)