Cache actions and stores for easy introspection

[spoike]

Story

As a user
I want to find all created actions AND stores from Reflux module
So that I can: trigger actions AND/OR tap on what they emit in the browser console

Explanation

At the moment it is up to the web application to hold all the created actions and stores. This proposal is for creating a action and store cache that is exposed from e.g. Reflux._actions and Reflux._stores.

This makes it easier to do introspection from a browser console, and opens up the possibility to create browser extensions that can:

• tap into what data the actions and stores do emit
• create a map of actions and stores
• easily trigger an action for development testing

[spoike]

As a first step, added a Reflux.__keep that contains createdActions and createdStores arrays. Hopefully this is enough to make a simple browser extension.

[undoZen]

I've done similar things in my module reflux-dispatcher

[spoike]

@undoZen 👍

Unfortunately I still haven't looked into hot reload scenario yet or had the time to review the reflux-dispatcher project yet. I do think people are free to use reflux-dispatcher if they need this functionality. :-)

[undoZen]

@spoike
I've been thinking about doing right on async progressing and writing isomorphic modules run on both client and server side like yahoo's flux example. Too bad that I don't have time to share my experience and track your discussion here in deep.