{"push_id":682353240,"size":1,"distinct_size":1,"ref":"refs/heads/reflux","head":"322755261377a80dfcc2d2b3e8d3e0a0cad97b27","before":"f645e9a642674ce606337beb947ba15131c245c4","commits":[{"sha":"322755261377a80dfcc2d2b3e8d3e0a0cad97b27","author":{"email":"34c6fceca75e456f25e7e99531e2425c6c1de443@stevenocchipinti.com","name":"Steve Occhipinti"},"message":"Introduce Reflux - Not yet being used properly\n\nI'm essentially using Reflux as just a pub/sub right now.\n\nThere should be a parent react component with the state of the event\n(timeslots, etc.), which then passes that down to its descendants via\nprops. The lower components should then use the actions to trigger an\nupdate that the top level element is subscribed to so it can update its\nstate and let the descendants reflect the changes.\n\nHere is some small example apps:\n - https://github.com/spoike/refluxjs-todo\n - https://github.com/limelights/todo-reflux\n\nHere is a tutorial:\n - http://www.sitepoint.com/creating-note-taking-app-react-flux/","distinct":true,"url":"https://api.github.com/repos/stevenocchipinti/schedulator-web/commits/322755261377a80dfcc2d2b3e8d3e0a0cad97b27"}]}