I'm curious what you'd think of react-easy-state and react-easy-params.
Also, in application after application, I keep getting screwed up by my tendency to implement everything with classes, especially now that ES6 etc. has a decent syntax for them. But then my objects end up not serializable, so saving stuff to redux or easy-state or anything else ends up with horrible kludges. Also, I've got a lot of complex (read-only) remote data I have to query, so I got excited a couple months ago by Apollo link state, but that totally befuddled me. I'll check out Unstated.
Very helpful synopsis; thank you!
I'm curious what you'd think of react-easy-state and react-easy-params.
Also, in application after application, I keep getting screwed up by my tendency to implement everything with classes, especially now that ES6 etc. has a decent syntax for them. But then my objects end up not serializable, so saving stuff to redux or easy-state or anything else ends up with horrible kludges. Also, I've got a lot of complex (read-only) remote data I have to query, so I got excited a couple months ago by Apollo link state, but that totally befuddled me. I'll check out Unstated.
Yep – it can be tricky with Apollo link state. If you're already querying remote state, Apollo has some benefits for the local state too.
What type of use case do you have for serializing whole objects to your state? I wonder if there would be ways of not needing to do that at all.