Keep global state? about crush2020

[camdenlee]

@jlev I can take this on. Can you point me to the areas in the application you'd want to use global state? I did a quick search for useState and found a few items, but all of them might not necessitate global state.

This might not need the complexity of Redux and React Context could do the trick instead. Do you have a strong preference?

[jlev]

Thanks @camdenlee! The form has a context provider in https://github.com/spacedogXYZ/crush2020/blob/master/src/components/form/context.js, which is used in the PlanForm component. That's pretty close to redux style (reducers, etc), and works to keep track of user state when they progress normally through the flow.

But, I'm seeing some weird issues when someone navigates away from the form (to eg, Methodology) and then back. Progress is lost, which is not a deal breaker but isn't a great experience. The worst problem is that when you reload a form step (even the first one), it renders with a broken layout which doesn't make sense to me...

• After navigating to form/vote directly

• After starting to fill out the form and then reloading

[jlev]

Fixed with #19