25 ms·
>1. Why marry the state stored in the database with any particular implementation of the front-end? They seem to have only one front-end implementation to worr
by uhoh-itsmaciek 7y ago
>1. Why marry the state stored in the database with any particular implementation of the front-end?
They seem to have only one front-end implementation to worry about for now, and the client state is most likely pretty generic (they don't really make this clear, but I can't think of anything react-specific you'd want to store in a reducer state).
- gary_bernhardt 7y agoThis is right. You'd have to read a ton of our source code to see this first hand, but the reducer state has nothing about React in it. It's a lot of stuff like "what answers did the user give?"; "was the answer correct or not?"; "what were the start and end timestamps for each attempt?"; etc. If we maintained multiple clients, we could reuse that structure because it's all about the application, not about React.