Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
redux-saga-selector-channel
Advanced tools
Readme
Create a redux-saga channel which updates with changes to a selector function.
import { buffers } from 'redux-saga';
import { takeEvery } from 'redux-saga/effects';
import selectorChannel from 'redux-saga-selector-channel';
// ...
function* selectorSaga(selectorOutput) {
// Use `selectorOutput` here, yield effects, do whatever you do in a saga!
}
// ...
function* mainSaga() {
const chan = yield selectorChannel(selector, buffers.expanding(10));
yield takeEvery(chan, selectorSaga);
}
// ...
selectorChannel
(default export)This package exports a single function which takes one or two arguments. The first argument is a selector function which will be passed the state of the redux store. The second argument is an optional buffer.
This function returns a call
effect which must be yield
ed to the
redux-saga runtime. The result will be a channel you can use in the same
way as any other redux-saga channel (take
, takeEvery
, takeLatest
,
etc). The contents of the channel will consist of each new output from the
selector function (determined with ===
).
Do not yield any effects from any saga which is handling output from your selector which will cause the selector to create a new output! This will cause an infinite loop. For a concrete example, consider the following:
// DO NOT DO THIS!
function* selectorSaga(counter) {
yield put(incrementCounter());
}
function* mainSaga() {
const chan = yield selectorChannel(state => state.counter);
yield takeEvery(chan, selectorSaga);
}
The selector function in this case returns the current counter
value and the
saga running in response to the selector output changing itself put
s an event
which changes the counter
value. This causes an infinite loop! It is okay to
put
from a selector response saga, but you have to be careful not to cause
infinite loops.
This package uses non-transpiled generator functions in order to give you the
flexibility to either use native generator functions or transpile them
yourself. If you need to support browsers that do not natively support
generator functions, make sure you configure your build to transpile this
package! In a setup using webpack the easiest way to do this is to use
Rule.include
and explitily include your source directories as well as the
resolved path to this module (rather than using Rule.exclude
to exclude
node_modules
and then somehow excluding this package from Rule.exclude
).
This package also doesn't have a main
field, only a module
field. As long
as you are using a modern build system this should not be a problem.
This package is simply a TypeScript packaging of
redux-saga/redux-saga#1694
. There may be future changes to support
passing additional arguments to the selector function (as is already supported
in the select
effect). Pull requests welcome!
MIT
FAQs
Create a redux-saga channel which updates with changes to a selector function.
The npm package redux-saga-selector-channel receives a total of 0 weekly downloads. As such, redux-saga-selector-channel popularity was classified as not popular.
We found that redux-saga-selector-channel demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.