DFO-Ocean-Navigator
Integrate Redux
From what I've read, the Navigator is a textbook use case for combining React + Redux. Prime example: changing datasets requires state changes to be propagated up the component tree and then back down to several other combo boxes and the map. Redux eliminates this spaghetti factory by using a shared global state tree that is decoupled from the UI (React) entirely. This would allow us to manipulate the UI (a.k.a redesign it) independently from our established "model" logic.
https://stackoverflow.com/questions/36631761/when-should-i-add-redux-to-a-react-app
Depending on how things go when I get back, I'm thinking this will be the first thing I bite into since from an engineering standpoint it's very high priority. Product-wise the UI is pretty much tied to the logic which is a big no-no for evolving anything.
We should discuss this when we both get back since I pretty much flipped the data upside down (data is stored at the edge now). This might not be the best approach, but it allowed me to add and remove things at will without affecting the whole navigator. My approach had some issues I wanted to discuss solutions for anyway.
