Skip to content

Redux Example #61

Open
Open

Description

@ericclemmons

Using v1:

http://gaearon.github.io/redux/

Also, this should be a form example, IMO. Something to warrant the router, but also having a store.

Activity

  1. added this to the v2 milestone on Aug 10, 2015
  2. josebalius commented on Aug 20, 2015

    @josebalius

    +1 looking forward to the redux example

  3. aripalo commented on Aug 21, 2015

    @aripalo

    Sorry to turns this to a "+1 thread", but +1 from me as well. Though I'm probably going to start (trying to) implementing react-resolver + redux in next few weeks so if no one else have done the example before that, I might be able to put together something... though I'm pretty new to React ecosystem, so not sure if my examples will be any good :D

  4. ericclemmons commented on Aug 21, 2015

    @ericclemmons
    OwnerAuthor
  5. ericclemmons commented on Aug 21, 2015

    @ericclemmons
    OwnerAuthor

    Which...actually didn't work haha.

    Thanks for your support! I'll be doing some TDD tonight for this (Tequila Driven Development).

  6. josebalius commented on Aug 21, 2015

    @josebalius

    @ericclemmons best kind of development right there! lol

  7. aripalo commented on Aug 21, 2015

    @aripalo

    Hahaha I might be doing npm install redux --save & keeping up the Ballmer Peak with some Beer Driven Development as well :D

  8. arush commented on Aug 26, 2015

    @arush

    well in that case, +1

  9. ericclemmons commented on Sep 14, 2015

    @ericclemmons
    OwnerAuthor

    This should also how how to handle #82

  10. RanzQ commented on Sep 19, 2015

    @RanzQ

    I'm using redux with redux-api-middleware. With @connect I can easily bind my store to the components but I haven't found a nice way to provide the initial state for the store. I'm also using (read: trying to use) server-side rendering with multiple routes (react-router) and code splitting so I was thinking if react-resolver could solve the problem to populate the state based on current route component. :)

    Just sharing my thoughts. +1

  11. RanzQ commented on Sep 19, 2015

    @RanzQ

    A better solution might be to use redux-promise (more discussion: redux #99). Using that I think it would be possible to call the needed async actions on @resolve and return an asyncAction() or Promise.all(asyncActions). That way the component will have its initial data in redux store before rendering. Somewhat similar what @erikras does with fetchData. I will try this later.

  12. jachenry commented on Sep 21, 2015

    @jachenry

    @RanzQ that's a great idea. maybe it'd be possible to chain @connect with @resolve so that the props passed to @resolve have the action creators and state necessary for loading data. Using this strategy would require us to somehow pass the state/creators through to the react component.

  13. anaibol commented on Oct 22, 2015

    @anaibol

    +1

  14. sars commented on Dec 31, 2015

    @sars

    +1

  15. AriaFallah commented on Feb 3, 2016

    @AriaFallah

    So is there any example usage with redux?

  16. sars commented on Feb 3, 2016

    @sars
  17. AriaFallah commented on Feb 3, 2016

    @AriaFallah

    @sars Thanks! I'll take a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions