-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to redux-saga 1.0.2 #29
base: master
Are you sure you want to change the base?
Conversation
New redux-saga 1.0.0 introduced some breaking changes, which changed the path for the effects used. This commit updates that path and some other related modules: - React, react-dom, react-router, redux, redux-saga, redux-saga-test-plan (beta, as is the only version supporting 1.0.0) - Update redux-saga-test-plan for working version, but still in PR
|
||
// eslint-disable-next-line import/namespace | ||
export const all = sagaEffects.all || (effects => effects); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still needed?
CI is failing atm, because |
Update redux-saga to v1.0.1
@jfairbank I know you're busy atm, but any chance you can merge this? With the latest beta of |
Is this PR going to be merged soon? |
Hey @jfairbank could you please consider merging that PR? |
Why:
path for the effects used.
This change addresses the issue by:
redux-saga-test-plan (Beta 2, as is the only version correctly supporting redux-saga 1.0.0)