Jason Miller

```js import createStore from 'unistore'; // The top-level state properties you want to persist const KEYS_TO_SAVE = ['foo', 'bar', 'baz']; const store = createStore(loadState() || INITIAL_STATE); // throttle saving let...

@Kanaye I totally forgot! Definitely use unissist - better to save to IndexedDB for sure.

This is a footgun, yes. In general, concurrent execution of actions that write to the same state properties is a bad idea, unless a locking mechanism is used: ```js actions...

I'm not sure! What does redux-logger do?

The trick here is that it becomes difficult to memoize `mapActionsToProps` when it contains nested objects. Maybe something like the select() function that powers `mapStateToProps` could work here?

Definitely an interesting prospect! I wouldn't have much of an idea where to start with it. Maybe by looking at how veux works?

Hmm - do you have an example of where this is needed? ```js function combineReducers(...fns) { return (...args) => Object.assign(...fns.map( fn => fn(...args) ); } ```

Neat! I'm open to adding this if it's plausible without much of a size increase. One issue I can see is that the subscriptions array needs to include the slice....

If there is a way to extra & reuse the logic from connect so the size stays down I'd be up for it!

I don't think we have a way to infer the types of mapStateToProps and mapActionToProps automatically, so you have to type them and use `connect`.