RESTED
RESTED copied to clipboard
Bump redux-saga from 0.14.3 to 1.2.1
Bumps redux-saga from 0.14.3 to 1.2.1.
Release notes
Sourced from redux-saga's releases.
@redux-saga/core@1.2.1Patch Changes
#2324
2466c79Thanks@neurosnap! - Add LICENSE fileUpdated dependencies [
2466c79]:
@redux-saga/deferred@1.2.1Patch Changes
- #2324
2466c79Thanks@neurosnap! - Add LICENSE file
@redux-saga/delay-p@1.2.1Patch Changes
#2324
2466c79Thanks@neurosnap! - Add LICENSE fileUpdated dependencies [
2466c79]:
@redux-saga/symbols@1.1.3
@redux-saga/types@1.2.1Patch Changes
- #2324
2466c79Thanks@neurosnap! - Add LICENSE file[email protected]
Patch Changes
#2324
2466c79Thanks@neurosnap! - Add LICENSE fileUpdated dependencies [
2466c79]:
@redux-saga/core@1.2.1
@redux-saga/core@1.2.0Minor Changes
#2295
bed4458Thanks@lourd! - Adds type inference for result of task returned from runSaga and SagaMiddleware.run#2296
612cae8Thanks@lourd! - Updates Channel type to eliminate void-emitting pitfall#2308
8207e33Thanks@Andarist,@neurosnap! -exportsfield has been added to thepackage.jsonmanifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.This should fix the compatibility with Node.js ESM support.
... (truncated)
Changelog
Sourced from redux-saga's changelog.
Changes from v0.16.0 to v1.0.0
During work on v1, we made several breaking changes
Breaking changes
- errors thrown during put execution are no longer caught and swallowed, you need to catch them manually
- errors thrown during cancellation process are no longer swallowed, you need to keep
finallyblock fail-safe- removed some deprecated APIs -
takeEvery,takeLatest,throttlefrom the redux-saga entry point (they are and were importable fromredux-saga/effects).put.syncandtakemwere removed.- removing execution of an array of effects
yield [...]. usealleffect instead.delaybecame an effect, olddelayfunction (not effect!) can be imported from@redux-saga/delay-pput.resolvewas changed toputResolvetake.maybewas changed totakeMaybe- changed API of runSaga - it no longer accepts subscribe option, you should create a channel (preferably stdChannel), pass it as channel argument to the runSaga API and communicate with through it with
takeandputmethodstask.donegetter was changed to betask.toPromisemethodonErrordoesn't extenderrorwith additional fieldsagaStack, but pass it as a property of second argument. before:onError: (e: Error), after:onError(e: Error, { sagaStack })Effectshape, yielded to redux-saga middleware, is stabilized and declared now as a plain JavaScript object- channels private getters (takers and closed) got removed
{effects, utils}aren't imported from 'redux-saga' anymore. imports them fromredux-saga/effects,redux-saga/utilsishelper should be imported from@redux-saga/is.createMockTask,cloneableGeneratorshould be imported from@redux-saga/testing-utils- now
raceshould be finished if any of effects resolved withEND(by analogy with all)- cancel and join cannot receive variadic arguments anymore. so you have to rewrite
cancel(...[tasks])andjoin(...[tasks])tocancel([tasks])andjoin([tasks])respectively. also callingcancel(...)returns a cancel-effect (before it may return analleffect), and callingjoin(...)returns a join-effect.- refactor effect structure from
{[IO]: true, [type]: payload }to{ [IO]: true, type, payload }to get rid of dynamictypeproperty. Could affect you if implement custom monitor for saga effects.- channel and actionChannel have default buffer of buffers.expanding()
- eventChannel does no longer accept matcher argument.
- exported util of
arrayOfDefferedgot renamed to the correctarrayOfDeferredNew functionality
- multicastChannel - no buffering, notify all pending takers, multicastChannel#take(cb, matcher = matchers.wildcard)
- support for
yield take(multicastChannel, pattern)- internal stdChannel got reworked to be a singleton object (it is wrapped multicastChannel's instance'), also it is an exported API to support new runSaga's signature - this should also result in being a small perf boost
effectMiddlewares- useful especially for testing, you can intercept/hijack any effect and resolve it on your own - passing it very redux-style to the next middleware (last being redux-saga itself). How it might be used can be checked here. Many thanks to@eloytorofor this featuretakeLeadinghelper. It takes "leading" action and ignores all incoming ones of the same type while the "leading" is still handled (useful for things debouncing)retryhelper. Receives a function and executes it (with blocking call). In case of failure will try to make another call afterdelayLengthmilliseconds, if a number of attempts <maxTriesparameter- add
debouncehelper. Spawns asagaon an action dispatched to the Store that matchespattern. Saga will be called after it stops takingpatternactions formsmilliseconds. Purpose of this is to prevent calling saga until the actions are settled off.
Commits
29a1ec3Version Packages (#2325)2466c79Add LICENSE files (#2324)bb056d2Version Packages (#2322)6f07fcaReplace all references to themasterbranch withmain1b71552UseonlyUpdatePeerDependentsWhenOutOfRange38903baUpgrade Changesets and some CI setups (#2321)979b8b4Add changeset aboutexportsfield being added to thepackage.jsonmanifests8207e33exportsfield has been added to thepackage.jsonmanifests (#2308)87cfaafadd missing export syntax for delay function, helloSaga, incrementAsync & wat...7e53ac2Add not working on RN disclaimer to babel-plugin Readme (#2220)- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by redux-saga-release-bot, a new releaser for redux-saga since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)