Yes, but redux-toolkit missed several things important for me, hence I created redux-smart-actions. Things I missed:
1) I don't like syntax like const doSomething = createAction('doSomething'), with my library you don't need to pass this duplicated name at all, saving you a little time and name duplication
2) createSmartAction from my lib has an automatic ability to protect against type collisions
3) toolkit doesn't have something like createThunk - thunks creator with attached constants like for normal actions
4) I know that 1, 2 is partially solved by slices, but I don't like them, for one thing I prefer writing actions as top level functions, another thing is that slices create reducers, and often I use global reducers and distributed actions, usually with my another library github.com/klis87/redux-requests
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi,
Yes, but redux-toolkit missed several things important for me, hence I created
redux-smart-actions. Things I missed:1) I don't like syntax like
const doSomething = createAction('doSomething'), with my library you don't need to pass this duplicated name at all, saving you a little time and name duplication2)
createSmartActionfrom my lib has an automatic ability to protect against type collisions3) toolkit doesn't have something like
createThunk- thunks creator with attached constants like for normal actions4) I know that 1, 2 is partially solved by slices, but I don't like them, for one thing I prefer writing actions as top level functions, another thing is that slices create reducers, and often I use global reducers and distributed actions, usually with my another library github.com/klis87/redux-requests