Ignite: Redux-Thunk instead of Redux-Saga in Ignite generated code

Created on 6 Dec 2016  路  11Comments  路  Source: infinitered/ignite

Can we use redux-thunk instead of redux-saga in Ignite generated application?

Most helpful comment

The --empty or --min app templates both support DIY state management. Creating your own generators in Ignite 2.0 is really straight forward. We have some docs now in place for this, but I think a few videos would go a long way!

Thanks all!

All 11 comments

This will be available as a feature in Ignite 2.0 - I'll leave this ticket open and help you get started when we release 2.0 for beta testing.

@GantMan expected date of release of ignite 2.0?

I'm hoping for early January

Does this mean removing Saga's?

sagas will not be removed. We'll simply make it easy for people to customize (and if they go with Thunk, they will probably remove sagas) but we won't be managing the Thunk plugin.

This is good, @GantMan. I think it might be very good have options: Sagas, Thunk, Loop, others. Cool!

The --empty or --min app templates both support DIY state management. Creating your own generators in Ignite 2.0 is really straight forward. We have some docs now in place for this, but I think a few videos would go a long way!

Thanks all!

How can we opt out of redux-saga and instead just use redux-thunk when creating a new (Ignite CLI 2) app ?

We haven't started it yet, but we plan to move Saga to a plugin, I believe.

Have you looked into or considered making a thunk plugin? Then you'd just have to remove Saga by hand, and then install your thunk plugin.

I'd love to create a thunk plugin, how can I get started / example etc ?

https://github.com/infinitered/ignite/blob/master/docs/advanced-guides/creating-plugins.md

Come join us on community.infinite.red if you need some realtime help.

Was this page helpful?
0 / 5 - 0 ratings