No need redux if I use swr?

[devhyunjae]

Hi guys,

Thanks for the awesome lib.

If i use redux + react. the usual flow is,

1. dispatch action -> redux saga or redux thunk -> api call
2. set the response data to global sate
3. get the state as props in the target component

Boring job...☹️

But!
If i use swr, smells like no need these steps any more.
I just have to call useUser() in every component where i need.

No worries about multiple duplicated request,
No need to handle global state or context any more.
No need all that kind of annoying actions, constants, reducers, sagas and etc redux family.

Am I right?

or is there exception cases to use redux or other state managing lib?

So excited to try this in next project :)

[sergiodxa]

I haven't used Redux again since I started using SWR, most of the time the only global data you put in Redux is API state, with SWR that data is on SWR cache so there is no need for Redux.

However, you may still want to have global state, in that case you can rely on Redux, Context, MobX or any other solution, IMO most of the time with only using useState/useReducer + Context is enough. If you think most of the global state of your app are things like the current theme (you will use a ThemeProvider for that usually), internationalization (you will use an IntlProvider for that) and a few custom things you may need for which you could create a specific provider to each type of data and avoid setting up Redux with all the required boilerplate or adding more complementary libraries to reduce the boilerplate.

[devhyunjae]

Thanks for the fast response!

[abdelhamid-attaby]

@sergiodxa @devhyunjae we created a package to handle the global state (either persisted or not). Please check https://www.npmjs.com/package/@zyda/swr-internal-state

[gadingnst]

@sergiodxa @devhyunjae @abdelhamid-attaby or you can use this too, it's simpler than Context API, no need to use Context API again. https://www.npmjs.com/package/swr-global-state

[windmaomao]

Just curious why "However, you may still want to have global state, in that case you can rely on Redux, Context, MobX or any other solution.". Because from the usage

    useSWR(key, fetcher)

no one said fetcher has to be an API, can it be a promise which just return anything. I'm just curious. Thanks.

[codthing]

Just curious why "However, you may still want to have global state, in that case you can rely on Redux, Context, MobX or any other solution.". Because from the usage

    useSWR(key, fetcher)

no one said fetcher has to be an API, can it be a promise which just return anything. I'm just curious. Thanks.

This is a good entry point for swr, indeed, fetcher is not necessarily api, but swr do not clearly describe the beginning and endding. I hope my understanding is not wrong.