
Research
/Security News
60 Malicious Ruby Gems Used in Targeted Credential Theft Campaign
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
redux-detector
Advanced tools
Redux enhancer for pure detection of state changes.
Warning: API is not stable yet, will be from version 1.0
Redux Detector requires Redux 3.1.0 or later.
npm install --save redux-detector
This assumes that you’re using npm package manager with a module bundler like Webpack or Browserify to consume CommonJS modules.
To enable Redux Detector, use createDetectorEnhancer
:
import { createStore } from 'redux';
import { createDetectorEnhancer } from 'redux-detector';
import rootReducer from './reducers';
import rootDetector from './detectors';
const store = createStore(
rootReducer,
createDetectorEnhancer(rootDetector)
);
Redux Detector enhancer allows you to detect state changes in redux. A detector is a simple and pure function which compares two states and returns action or list of actions for some states transitions.
type Detector<S> = (prevState: S | undefined, nextState: S | undefined) => Action | Action[] | void;
For example detector that checks if number of rows exceed 100 looks like this:
function rowsLimitExceededDetector(prevState, nextState) {
if (prevState.rows.length <= 100 && nextState.rows.length > 100) {
return { type: ROWS_LIMIT_EXCEEDED };
}
}
You can also return an array of actions or nothing (undefined). Thanks to detectors purity they are predictable and easy to test. There is no problem with features like time-travel, etc.
Redux store can handle only one detector (and one reducer). But don't worry - you can combine and reduce them. To do this, use
combineDetectors
and reduceDetectors
functions.
// ./detectors/rootDetector.js
import { combineDetectors, reduceDetectors } from 'redux-detector';
import { fooDetector } from './fooDetector';
import { barDetector } from './barDetector';
import { anotherDetector } from './anotherDetector';
// our state has shape:
// {
// foo: [],
// bar: 1
// }
//
// We want to bind `fooDetector` and `anotherDetector` to `state.foo` branch (they should run in sequence)
// and also `barDetector` to `state.bar` branch.
export default combineDetectors({
foo: reduceDetectors(
fooDetector,
anotherDetector
),
bar: barDetector
});
Another way to re-use local state detectors is to mount them with mountDetector
function. Combine detectors work only on objects level -
if you want to use detectors on more nested data, you should mount them. With factory pattern, it becomes very elastic.
// ./detectors/limitExceedDetector.js
export function createLimitExceedDetector(limit, action) {
return function limitExceedDetector(prevState, nextState) {
if (prevState <= limit && nextState > limit) {
return action;
}
}
}
// ./detectors/rowsLimitExceedDetector.js
import { mountDetector } from 'redux-detector';
import { createLimitExceeedDetector } from './limitExceedDetector';
export const rowsLimitExceedDetector = mountDetector(
state => state.rows.length,
createLimitExceedDetector(100, ROWS_LIMIT_EXCEEDED)
);
Of course, examples above are very trivial, but you can use it to solve more common problems (you can, for example, schedule resource fetch on parameters change).
Redux Detector provides replaceDetector
method on DetectableStore
interface (store created by Redux Detector). It's similar to
replaceReducer
- it changes detector and dispatches { type: '@@detector/INIT' }
.
If you are using TypeScript, you don't have to install typings - they are provided in npm package.
MIT
FAQs
Redux enhancer for pure detection of state changes.
The npm package redux-detector receives a total of 883 weekly downloads. As such, redux-detector popularity was classified as not popular.
We found that redux-detector 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.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.
Research
/Security News
Two npm packages masquerading as WhatsApp developer libraries include a kill switch that deletes all files if the phone number isn’t whitelisted.