[Doppins] Upgrade dependency redux-saga to 1.0.2

[doppins-bot]

Hi!

A new version was just released of redux-saga, so Doppins
has upgraded your project's dependency ranges.

Make sure that it doesn't break anything, and happy merging!

---

Upgraded redux-saga from 0.16.0 to 0.16.1

Changelog:

Version 1.0.0-beta.2

This release is highly motivated by our 2 new core members @restrry & @shinima. They have put a lot of work into creating PRs & helping others with their issues.

We've recently extracted some modular packages, you can see @redux-saga`/deferred`, @redux-saga/delay-p, @redux-saga`/is` & @redux-saga/symbols. At the same time we've managed to shave off some bytes from the core build - according to some tests of our we've managed remove over 1kb, but your YMMV ofc.

Added:

• retry effect with the signature of retry(maxTries, delayLength, worker, ...args)
• debounce effect with the signature of debounce(delayLength, pattern, worker, ...args)

Changed:

• {effects, utils} aren't imported from 'redux-saga' anymore. import them from redux-saga/effects, redux-saga/utils
• is helper should be imported from ``@redux-saga/is.
• delay function (not effect!) should be imported from ``@redux-saga/delay-p
• signature of join & cancel, they both accept now a single task descriptor or an array of those (previously they have accepted variadic length of arguments)
• refactored shape of the effect objects to { [IO]: true, type, payload }, their structure should be treated as opaque anyway, so we hope this doesn't break anyone
• END will now finish the race effects

Version 1.0.0-beta.1

Error handling

Let's face it. Errors coming from redux-saga were unreadable and made finding a root cause of the problem really difficult. We really want to improve this situation and with this release (thanks to @restrry's amazing contribution) we start to log "saga stacks" along with original errors. This works similar to what React already does with its "component stacks". Just look at this one:

You can even enhance those stacks with file names and line numbers by using in development our new babel-plugin-redux-saga (also thanks to @restrry). Let us know if there are any issues with this or if we can make them even more useful!

Also onError should get called now even if you throw non-Errors in your code.

Beside that few things have changed, you can read more about them below.

Added:

• takeLeading effect - it takes "leading" action and ignores all incoming ones of the same type while the "leading" is still handled (useful for things debouncing)
• redux@4 got in supported range (this will let npm dedupe redux in node_modules, keep in mind though that we only depend on compose from that package)

Changed:

• delay became an effect, you still can import delay util from redux-saga/utils though

Version 1.0.0-beta.0

I must say that this release probably wouldn't be possible without community sponsors - both organizations and individual backers.

I'm not saying that money given by the community has helped, but it is a nice incentive to work and a token of appreciation. Somehow the fact alone that people are sending money towards us got me lately back on track, going, writing some code, pushing things forward towards v1 release.

Note that the money is not what you have most valuable to offer for OSS projects - your time is way more valuable. If you want some feature to get implemented, bug to be fixed or just want to help - please reach out to a project's maintainer, maybe ask for pointers about code internals so you can start working easier. OSS is done by regular people like you and most projects' code is not magic, everything can be figured out and you can get comfortable with it.

Maintaining a popular project (over 10k ⭐️⭐️⭐️!) is not an easy task to do. Truth to be told you do not even have to write code to get exhausted. Answering issues, replying to people's demands etc is time and energy consuming.

I'd want to think that at least in those areas I've maintained the package well - nearly every question gets answered and it gets answered within days. I've helped people fix their broken code, I've suggested how their apps can be structured, how to solve particular problems.

However GitHub is not really a place where (most of such) questions should be asked. Whenever you consider asking a question on any project's GitHub, please consider if it is the right place to ask. There are many places you can get help from the community, such as obviously StackOverflow. In terms of redux-saga additionally you can reach out to the community on our gitter channel and redux-saga reactiflux's channel.

New:

• multicastChannel - no buffering, notify all pending takers, multicastChannel#take(cb, matcher = matchers.wildard)
• 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 (https://github.com/redux-saga/redux-saga/blob/34c9093684323ab92eacdf2df958f31d9873d3b1/test/interpreter/effectMiddlewares.js#L88). Many thanks to @eloytoro for this feature

Breaking changes:

• channel and actionChannel have default buffer of buffers.expanding()
• errors thrown during put execution are no longer caught and swallowed, you need to catch them manually
• eventChannel does no longer accept matcher argument - it was a hacky way to support previous implementation of stdChannel
• exported util of arrayOfDeffered got renamed to the correct arrayOfDeferred
• internal util of sym tries to use Symbol if it's available, this mainly breaks effects' "shape" - types no longer are simple strings, although no code should make any assumptions about effects' shape anyway
• removed some deprecated APIs - takeEvery, takeLatest, throttle from the redux-saga entry point (they are and were importable from redux-saga/effects), takem, put.sync and executing array of effects, there is explicit API for this for already some time - all effect
• 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 take and put methods
• most runtime type checks got hidden behing development checks, inputs might not be validated in production (failed validation resulted in error being thrown anyway)
• task.done getter was changed to be task.toPromise method
• channels private getters (__takers__ and __closed__) got removed

Bug fixes:

• keeping single stdChannel in the internals allowed to fix 2 bugs with missed actions (see #707 and #1146), cc @gajus

Internals:

• We have started to use babel@7-beta, hopefully it won't break anything. I've investigated differences between outputs and everything seems to be ok, but you never know ;) This should result in a little bit smaller and a little bit more performant code.

[doppins-bot]

An additional new version was just released of redux-saga, so we've added an
extra commit upgrading your range to 0.16.2.

Hope that's alright!
— Doppins

[doppins-bot]

An additional new version was just released of redux-saga, so we've added an
extra commit upgrading your range to 1.0.0.

Hope that's alright!
— Doppins

[doppins-bot]

An additional new version was just released of redux-saga, so we've added an
extra commit upgrading your range to 1.0.1.

Hope that's alright!
— Doppins

[doppins-bot]

An additional new version was just released of redux-saga, so we've added an
extra commit upgrading your range to 1.0.2.

Hope that's alright!
— Doppins