rebuild state management on frontend #65
Description
Existing State management
relies heavily on multiple data types meaning different things, and is confusing to read. Also control flow is not properly outlined, and states are forced to be frequently moved around as requirements of components change
Goal
Move to a new state management system & library. Each state should be single typed and enum equivalents should be used when possible. Instead of storing states in components randomly, map out all that is needed, store them centrally, and ascribe permissions dynamically