Michael Ridgway

Proposal: remove support for `emitChange` payloads in BaseStore

4

Payloads being emitted from `emitChange` can cause issues where state is actually being emitted rather than letting the store be used as the source of truth. This is problematic because...

[router] Better support for scroll state and positioning during navigation

1

See https://github.com/yahoo/fluxible-router/issues/59

[fluxible] Consider adding `executeAction` to store context

11

[Bill Fisher's talk](http://youtu.be/Bic_sFiaNDI?t=32m13s) and some of the [Flux articles](http://ianobermiller.com/blog/2014/09/15/react-and-flux-interview/) talk about performing API calls directly from the stores. The responses from these API calls should always go through an action...

See https://github.com/yahoo/fluxible-plugin-fetchr/issues/11

See https://github.com/yahoo/fluxible-plugin-fetchr/issues/27

See https://github.com/yahoo/fluxible-plugin-fetchr/issues/33

See https://github.com/yahoo/fluxible-router/issues/88

See https://github.com/yahoo/fluxible-router/issues/92

Investigate replay-based rehydration

8

Theoretically, stores could be reset to their original state by recording the actions and payloads that were dispatched on the server, serializing them, and then replaying them on the client...

- [x] Used appropriate template for the issue type - [x] Searched both open and closed issues for duplicates of this issue - [x] Title adequately and _concisely_ reflects the...