Gathering detailed insights and metrics for redux-query-sync
Gathering detailed insights and metrics for redux-query-sync
Gathering detailed insights and metrics for redux-query-sync
Gathering detailed insights and metrics for redux-query-sync
npm install redux-query-sync
Typescript
Module System
Node Version
NPM Version
71.4
Supply Chain
97.9
Quality
75
Maintenance
100
Vulnerability
100
License
JavaScript (100%)
Love this project? Help keep it running — sponsor us today! 🚀
Total Downloads
1,185,667
Last Day
298
Last Week
1,289
Last Month
7,826
Last Year
81,362
79 Stars
61 Commits
24 Forks
5 Watching
1 Branches
5 Contributors
Minified
Minified + Gzipped
Latest Version
0.1.10
Package Id
redux-query-sync@0.1.10
Unpacked Size
18.11 kB
Size
6.21 kB
File Count
5
NPM Version
6.14.6
Node Version
14.5.0
Cumulative downloads
Total Downloads
Last day
-16.1%
298
Compared to previous day
Last week
-23.6%
1,289
Compared to previous week
Last month
49.1%
7,826
Compared to previous month
Last year
-47.6%
81,362
Compared to previous year
2
3
Treat the URL query parameters as exposed variables of your Redux state. For example,
/mypage.html?p=14
could correspond to a state object containing {pageNumber: 14}
.
Any changes to the store state are reflected in the URL. Vice versa, if the URL is changed using the
history
module, the changed parameters are updated in the store state.
Similar modules exist, which you might prefer in some scenarios:
Router
(not
BrowserRouter
) and pass
to both modules the same history
instance (see this
explanation).Otherwise, keep reading.
npm install redux-query-sync
…or equivalent.
As a minimal example, let's say we want to synchronise query parameter dest
with the value of the
state's route.destination
field, to parse/make URLs such as directions.html?dest=Amsterdam
.
Minimal example
1import ReduxQuerySync from 'redux-query-sync'
2
3ReduxQuerySync({
4 store, // your Redux store
5 params: {
6 dest: {
7 // The selector you use to get the destination string from the state object.
8 selector: state => state.route.destination,
9 // The action creator you use for setting a new destination.
10 action: value => ({type: 'setDestination', payload: value}),
11 },
12 },
13 // Initially set the store's state to the current location.
14 initialTruth: 'location',
15})
Note that redux-query-sync does not modify the state, but lets you specify which action to dispatch when the state should be updated. It does modify the location (using history.pushState/replaceState), but ensures to only touch the parameters you specified.
Let's look at a more elaborate example now. We sync the query parameter p
with the value of the
state's pageNumber
field, which includes a mapping between string and integer.
Longer example
1import ReduxQuerySync from 'redux-query-sync'
2
3ReduxQuerySync({
4 store,
5 params: {
6 p: {
7 selector: state => state.pageNumber,
8 action: value => ({type: 'setPageNumber', payload: value}),
9
10 // Cast the parameter value to a number (we map invalid values to 1, which will then
11 // hide the parameter).
12 stringToValue: string => Number.parseInt(string) || 1,
13
14 // We then also specify the inverse function (this example one is the default)
15 valueToString: value => `${value}`,
16
17 // When state.pageNumber equals 1, the parameter p is hidden (and vice versa).
18 defaultValue: 1,
19 },
20 },
21 initialTruth: 'location',
22
23 // Use replaceState so the browser's back/forward button will skip over these page changes.
24 replaceState: true,
25})
Note you could equally well put the conversion to and from the string in the selector and action
creator, respectively. The defaultValue
should then of course be a string too.
See some examples in the wild:
Sets up bidirectional synchronisation between a Redux store and window location query parameters.
Param | Type | Description |
---|---|---|
options.store | Object | The Redux store object (= an object {dispatch, getState} ). |
options.params | Object | The query parameters in the location to keep in sync. |
options.params[].action | function: value => action | The action creator to be invoked with the parameter value. Should return an action that sets this value in the store. |
options.params[].selector | function: state => value | The function that gets the value given the state. |
[options.params[].defaultValue] | * | The value corresponding to absence of the parameter. You may want this to equal the state's default/initial value. Default: undefined . |
[options.params[].valueToString] | function | Specifies how to cast the value to a string, to be used in the URL. Defaults to javascript's automatic string conversion. |
[options.params[].stringToValue] | function | The inverse of valueToString. Specifies how to parse the parameter's string value to your desired value type. Defaults to the identity function (i.e. you get the string as it is). |
options.initialTruth | string | If set, indicates whose values to sync to the other, initially. Can be either 'location' or 'store' . If not set, the first of them that changes will set the other, which is not recommended. Usually you will want to use location . |
[options.replaceState] | boolean | If truthy, update location using history.replaceState instead of history.pushState , to not add entries to the browser history. Default: false |
[options.history] | Object | If you use the 'history' module, e.g. when using a router, pass your history object here in order to ensure all code uses the same instance. |
Returns: a function unsubscribe()
that can be called to stop the synchronisation.
For convenience, one can set up the synchronisation by passing an enhancer to createStore.
Example
1const storeEnhancer = ReduxQuerySync.enhancer({ 2 params, 3 initialTruth, 4 replaceState, 5}) 6const store = createStore(reducer, initialState, storeEnhancer)
Arguments to ReduxQuerySync.enhancer
are equal to those for ReduxQuerySync
itself, except that
store
can now of course be omitted. With this approach, you cannot cancel the synchronisation.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 4/27 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
25 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-02-03
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More