Component Store Example
Description
An example of the topics covered in Building for Plugins with React & Flux
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
README
Building for Plugins with React & Flux
This sample code demonstrates the concepts we discussed at [ReactEurope 2015](https://www.youtube.com/watch?v=Uu4Yz2HmCgE) in a small app that implements a message list with a "mark as read" plugin:
Using a single, central DataStore to eliminate store interdependencies and allow plugins to modify data in unexpected ways.
Using a ComponentStore to dynamically register and inject components at runtime.
Isolating the React.Render calls for third-party "unsafe" components.
Getting Started
To run the sample project, run the commands below and visit [http://localhost:9001](http://localhost:9001) in your browser.
npm install
bower install
grunt connectGet in touch!
We'd love your thoughts and feedback. Feel free to email us at `ben@nylas.com` and `evan@nylas.com`. If you think React and Flux are great, we're also [hiring](http://nylas.com/jobs)!
Related Skills
Auto Update
Pull the latest ECC repo changes and reinstall the current managed targets.
Ecc Guide
Navigate ECC's current agents, skills, commands, hooks, install profiles, and docs from the live repository su
Epic Claim
Claim an epic issue, stamp coordination state, and sync local ownership.
Epic Publish
Publish a validated epic update back to the issue and local cache.
Epic Review
Mark epic review requested, approved, or changes requested.
Epic Unblock
Sweep blocked epic issues and reopen anything whose dependencies are closed.