@wordpress/data
Advanced tools
WordPress' data module serves as a hub to manage application state for both plugins and WordPress itself, providing tools to manage data within and between distinct modules. It is designed as a modular pattern for organizing and sharing data: simple enough to satisfy the needs of a small plugin, while scalable to serve the requirements of a complex single-page application.
The data module is built upon and shares many of the same core principles of Redux, but shouldn't be mistaken as merely Redux for WordPress, as it includes a few of its own distinguishing characteristics. As you read through this guide, you may find it useful to reference the Redux documentation — particularly its glossary — for more detail on core concepts.
Install the module
npm install @wordpress/data --save
This package assumes that your code will run in an ES2015+ environment. If you're using an environment that has limited or no support for ES2015+ such as lower versions of IE then using core-js or @babel/polyfill will add support for these methods. Learn more about it in Babel docs.
Use the registerStore function to add your own store to the centralized data registry. This function accepts two arguments: a name to identify the module, and an object with values describing how your state is represented, modified, and accessed. At a minimum, you must provide a reducer function describing the shape of your state and how it changes in response to actions dispatched to the store.
const { apiFetch } = wp;
const { registerStore } = wp.data;
const DEFAULT_STATE = {
prices: {},
discountPercent: 0,
};
const actions = {
setPrice( item, price ) {
return {
type: 'SET_PRICE',
item,
price,
};
},
startSale( discountPercent ) {
return {
type: 'START_SALE',
discountPercent,
};
},
fetchFromAPI( path ) {
return {
type: 'FETCH_FROM_API',
path,
};
},
};
registerStore( 'my-shop', {
reducer( state = DEFAULT_STATE, action ) {
switch ( action.type ) {
case 'SET_PRICE':
return {
...state,
prices: {
...state.prices,
[ action.item ]: action.price,
},
};
case 'START_SALE':
return {
...state,
discountPercent: action.discountPercent,
};
}
return state;
},
actions,
selectors: {
getPrice( state, item ) {
const { prices, discountPercent } = state;
const price = prices[ item ];
return price * ( 1 - ( 0.01 * discountPercent ) );
},
},
controls: {
FETCH_FROM_API( action ) {
return apiFetch( { path: action.path } );
},
},
resolvers: {
* getPrice( item ) {
const path = '/wp/v2/prices/' + item;
const price = yield actions.fetchFromAPI( path );
return actions.setPrice( item, price );
},
},
} );
The return value of registerStore is a Redux-like store object with the following methods:
store.getState(): Returns the state value of the registered reducer
getStatestore.subscribe( listener: Function ): Registers a function called any time the value of state changes.
subscribestore.dispatch( action: Object ): Given an action object, calls the registered reducer and updates the state value.
dispatchreducerA reducer is a function accepting the previous state and action as arguments and returns an updated state value.
actionsThe actions object should describe all action creators available for your store. An action creator is a function that optionally accepts arguments and returns an action object to dispatch to the registered reducer. Dispatching actions is the primary mechanism for making changes to your state.
selectorsThe selectors object includes a set of functions for accessing and deriving state values. A selector is a function which accepts state and optional arguments and returns some value from state. Calling selectors is the primary mechanism for retrieving data from your state, and serve as a useful abstraction over the raw data which is typically more susceptible to change and less readily usable as a normalized object.
resolversA resolver is a side-effect for a selector. If your selector result may need to be fulfilled from an external source, you can define a resolver such that the first time the selector is called, the fulfillment behavior is effected.
The resolvers option should be passed as an object where each key is the name of the selector to act upon, the value a function which receives the same arguments passed to the selector, excluding the state argument. It can then dispatch as necessary to fulfill the requirements of the selector, taking advantage of the fact that most data consumers will subscribe to subsequent state changes (by subscribe or withSelect).
controlsNote: Controls are an opt-in feature, enabled via use (the Plugins API).
A control defines the execution flow behavior associated with a specific action type. This can be particularly useful in implementing asynchronous data flows for your store. By defining your action creator or resolvers as a generator which yields specific controlled action types, the execution will proceed as defined by the control handler.
The controls option should be passed as an object where each key is the name of the action type to act upon, the value a function which receives the original action object. It should returns either a promise which is to resolve when evaluation of the action should continue, or a value. The value or resolved promise value is assigned on the return value of the yield assignment. If the control handler returns undefined, the execution is not continued.
Refer to the documentation of @wordpress/redux-routine for more information.
initialStateAn optional preloaded initial state for the store. You may use this to restore some serialized state value or a state generated server-side.
The @wordpress/data module offers a more advanced and generic interface for the purposes of integrating other data systems and situations where more direct control over a data system is needed. In this case, a data store will need to be implemented outside of @wordpress/data and then plugged in via three functions:
getSelectors(): Returns an object of selector functions, pre-mapped to the store.getActions(): Returns an object of action functions, pre-mapped to the store.subscribe( listener: Function ): Registers a function called any time the value of state changes.
subscribe
with the following differences:
By implementing the above interface for your custom store, you gain the benefits of using the registry and the withSelect and withDispatch higher order components in your application code. This provides seamless integration with existing and alternative data systems.
Integrating an existing redux store with its own reducers, store enhancers and middleware can be accomplished as follows:
Example:
import existingSelectors from './existing-app/selectors';
import existingActions from './existing-app/actions';
import createStore from './existing-app/store';
const { registerGenericStore } = wp.data;
const reduxStore = createStore();
const mappedSelectors = Object.keys( existingSelectors ).reduce( ( acc, selectorKey ) => {
acc[ selectorKey ] = ( ...args ) =>
existingSelectors[ selectorKey ]( reduxStore.getState(), ...args );
return acc;
}, {} );
const mappedActions = Object.keys( existingActions ).reduce( ( acc, actionKey ) => {
acc[ actionKey ] = ( ...args ) => reduxStore.dispatch( existingActions[ actionKey ]( ...args ) );
return acc;
}, {} );
const genericStore = {
getSelectors() {
return mappedSelectors;
},
getActions() {
return mappedActions;
},
subscribe: reduxStore.subscribe,
};
registerGenericStore( 'existing-app', genericStore );
It is also possible to implement a completely custom store from scratch:
Example:
const { registerGenericStore } = wp.data;
function createCustomStore() {
let storeChanged = () => {};
const prices = { hammer: 7.50 };
const selectors = {
getPrice( itemName ) {
return prices[ itemName ];
},
};
const actions = {
setPrice( itemName, price ) {
prices[ itemName ] = price;
storeChanged();
},
};
return {
getSelectors() {
return selectors;
},
getActions() {
return actions;
},
subscribe( listener ) {
storeChanged = listener;
}
};
}
registerGenericStore( 'custom-data', createCustomStore() );
The data module shares many of the same core principles and API method naming of Redux. In fact, it is implemented atop Redux. Where it differs is in establishing a modularization pattern for creating separate but interdependent stores, and in codifying conventions such as selector functions as the primary entry point for data access.
The higher-order components were created to complement this distinction. The intention with splitting withSelect and withDispatch — where in React Redux they are combined under connect as mapStateToProps and mapDispatchToProps arguments — is to more accurately reflect that dispatch is not dependent upon a subscription to state changes, and to allow for state-derived values to be used in withDispatch (via higher-order component composition).
Specific implementation differences from Redux and React Redux:
subscribe listener is called on every dispatch, regardless of whether the value of state has changed.
@wordpress/data, a subscriber is only called when state has changed.mapStateToProps function must return an object.
@wordpress/data, a withSelect mapping function can return undefined if it has no props to inject.mapDispatchToProps argument can be defined as an object or a function.
@wordpress/data, the withDispatch higher-order component creator must be passed a function.# combineReducers
The combineReducers helper function turns an object whose values are different reducing functions into a single reducing function you can pass to registerReducer.
Usage
const { combineReducers, registerStore } = wp.data;
const prices = ( state = {}, action ) => {
return action.type === 'SET_PRICE' ?
{
...state,
[ action.item ]: action.price,
} :
state;
};
const discountPercent = ( state = 0, action ) => {
return action.type === 'START_SALE' ?
action.discountPercent :
state;
};
registerStore( 'my-shop', {
reducer: combineReducers( {
prices,
discountPercent,
} ),
} );
Parameters
Object: An object whose values correspond to different reducing functions that need to be combined into one.Returns
Function: A reducer that invokes every reducer inside the reducers object, and constructs a state object with the same shape.# createRegistry
Creates a new store registry, given an optional object of initial store configurations.
Parameters
Object: Initial store configurations.?Object: Parent registry.Returns
WPDataRegistry: Data registry.# createRegistryControl
Mark a control as a registry control.
Parameters
function: Function receiving a registry object and returning a control.Returns
function: marked registry control.# createRegistrySelector
Mark a selector as a registry selector.
Parameters
function: Function receiving a registry object and returning a state selector.Returns
function: marked registry selector.# dispatch
Given the name of a registered store, returns an object of the store's action creators. Calling an action creator will cause it to be dispatched, updating the state value accordingly.
Note: Action creators returned by the dispatch will return a promise when they are called.
Usage
const { dispatch } = wp.data;
dispatch( 'my-shop' ).setPrice( 'hammer', 9.75 );
Parameters
string: Store nameReturns
Object: Object containing the action creators.# plugins
Object of available plugins to use with a registry.
Related
Type
Object# registerGenericStore
Registers a generic store.
Parameters
string: Store registry key.Object: Configuration (getSelectors, getActions, subscribe).# registerStore
Registers a standard @wordpress/data store.
Parameters
string: Reducer key.Object: Store description (reducer, actions, selectors, resolvers).Returns
Object: Registered store object.# RegistryConsumer
A custom react Context consumer exposing the provided registry to
children components. Used along with the RegistryProvider.
You can read more about the react context api here: https://reactjs.org/docs/context.html#contextprovider
Usage
const {
RegistryProvider,
RegistryConsumer,
createRegistry
} = wp.data;
const registry = createRegistry( {} );
const App = ( { props } ) => {
return <RegistryProvider value={ registry }>
<div>Hello There</div>
<RegistryConsumer>
{ ( registry ) => (
<ComponentUsingRegistry
{ ...props }
registry={ registry }
) }
</RegistryConsumer>
</RegistryProvider>
}
<a name="RegistryProvider" href="#RegistryProvider">#</a> **RegistryProvider**
A custom Context provider for exposing the provided `registry` to children
components via a consumer.
See <a name="#RegistryConsumer">RegistryConsumer</a> documentation for
example.
<a name="select" href="#select">#</a> **select**
Given the name of a registered store, returns an object of the store's selectors.
The selector functions are been pre-bound to pass the current state automatically.
As a consumer, you need only pass arguments of the selector, if applicable.
*Usage*
```js
const { select } = wp.data;
select( 'my-shop' ).getPrice( 'hammer' );
Parameters
string: Store nameReturns
Object: Object containing the store's selectors.# subscribe
Given a listener function, the function will be called any time the state value
of one of the registered stores has changed. This function returns a unsubscribe
function used to stop the subscription.
Usage
const { subscribe } = wp.data;
const unsubscribe = subscribe( () => {
// You could use this opportunity to test whether the derived result of a
// selector has subsequently changed as the result of a state update.
} );
// Later, if necessary...
unsubscribe();
Parameters
Function: Callback function.# use
Extends a registry to inherit functionality provided by a given plugin. A plugin is an object with properties aligning to that of a registry, merged to extend the default registry behavior.
Parameters
Object: Plugin object.# useDispatch
A custom react hook returning the current registry dispatch actions creators.
Note: The component using this hook must be within the context of a RegistryProvider.
Usage
This illustrates a pattern where you may need to retrieve dynamic data from
the server via the useSelect hook to use in combination with the dispatch
action.
const { useDispatch, useSelect } = wp.data;
const { useCallback } = wp.element;
function Button( { onClick, children } ) {
return <button type="button" onClick={ onClick }>{ children }</button>
}
const SaleButton = ( { children } ) => {
const { stockNumber } = useSelect(
( select ) => select( 'my-shop' ).getStockNumber()
);
const { startSale } = useDispatch( 'my-shop' );
const onClick = useCallback( () => {
const discountPercent = stockNumber > 50 ? 10: 20;
startSale( discountPercent );
}, [ stockNumber ] );
return <Button onClick={ onClick }>{ children }</Button>
}
// Rendered somewhere in the application:
//
// <SaleButton>Start Sale!</SaleButton>
Parameters
[string]: Optionally provide the name of the store from which to retrieve action creators. If not provided, the registry.dispatch function is returned instead.Returns
Function: A custom react hook.# useRegistry
A custom react hook exposing the registry context for use.
This exposes the registry value provided via the
Registry Provider to a component implementing
this hook.
It acts similarly to the useContext react hook.
Note: Generally speaking, useRegistry is a low level hook that in most cases
won't be needed for implementation. Most interactions with the wp.data api
can be performed via the useSelect hook, or the withSelect and
withDispatch higher order components.
Usage
const {
RegistryProvider,
createRegistry,
useRegistry,
} = wp.data
const registry = createRegistry( {} );
const SomeChildUsingRegistry = ( props ) => {
const registry = useRegistry( registry );
// ...logic implementing the registry in other react hooks.
};
const ParentProvidingRegistry = ( props ) => {
return <RegistryProvider value={ registry }>
<SomeChildUsingRegistry { ...props } />
</RegistryProvider>
};
Returns
Function: A custom react hook exposing the registry context value.# useSelect
Custom react hook for retrieving props from registered selectors.
In general, this custom React hook follows the rules of hooks.
Usage
const { useSelect } = wp.data;
function HammerPriceDisplay( { currency } ) {
const price = useSelect( ( select ) => {
return select( 'my-shop' ).getPrice( 'hammer', currency )
}, [ currency ] );
return new Intl.NumberFormat( 'en-US', {
style: 'currency',
currency,
} ).format( price );
}
// Rendered in the application:
// <HammerPriceDisplay currency="USD" />
In the above example, when HammerPriceDisplay is rendered into an
application, the price will be retrieved from the store state using the
mapSelect callback on useSelect. If the currency prop changes then
any price in the state for that currency is retrieved. If the currency prop
doesn't change and other props are passed in that do change, the price will
not change because the dependency is just the currency.
Parameters
Function: Function called on every state change. The returned value is exposed to the component implementing this hook. The function receives the registry.select method on the first argument and the registry on the second argument.Array: If provided, this memoizes the mapSelect so the same mapSelect is invoked on every state change unless the dependencies change.Returns
Function: A custom react hook.# withDispatch
Higher-order component used to add dispatch props using registered action creators.
Usage
function Button( { onClick, children } ) {
return <button type="button" onClick={ onClick }>{ children }</button>;
}
const { withDispatch } = wp.data;
const SaleButton = withDispatch( ( dispatch, ownProps ) => {
const { startSale } = dispatch( 'my-shop' );
const { discountPercent } = ownProps;
return {
onClick() {
startSale( discountPercent );
},
};
} )( Button );
// Rendered in the application:
//
// <SaleButton discountPercent="20">Start Sale!</SaleButton>
In the majority of cases, it will be sufficient to use only two first params
passed to mapDispatchToProps as illustrated in the previous example.
However, there might be some very advanced use cases where using the
registry object might be used as a tool to optimize the performance of
your component. Using select function from the registry might be useful
when you need to fetch some dynamic data from the store at the time when the
event is fired, but at the same time, you never use it to render your
component. In such scenario, you can avoid using the withSelect higher
order component to compute such prop, which might lead to unnecessary
re-renders of your component caused by its frequent value change.
Keep in mind, that mapDispatchToProps must return an object with functions
only.
function Button( { onClick, children } ) {
return <button type="button" onClick={ onClick }>{ children }</button>;
}
const { withDispatch } = wp.data;
const SaleButton = withDispatch( ( dispatch, ownProps, { select } ) => {
// Stock number changes frequently.
const { getStockNumber } = select( 'my-shop' );
const { startSale } = dispatch( 'my-shop' );
return {
onClick() {
const discountPercent = getStockNumber() > 50 ? 10 : 20;
startSale( discountPercent );
},
};
} )( Button );
// Rendered in the application:
//
// <SaleButton>Start Sale!</SaleButton>
Note: It is important that the mapDispatchToProps function always
returns an object with the same keys. For example, it should not contain
conditions under which a different value would be returned.
Parameters
Function: A function of returning an object of prop names where value is a dispatch-bound action creator, or a function to be called with the component's props and returning an action creator.Returns
Component: Enhanced component with merged dispatcher props.# withRegistry
Higher-order component which renders the original component with the current
registry context passed as its registry prop.
Parameters
WPComponent: Original component.Returns
WPComponent: Enhanced component.# withSelect
Higher-order component used to inject state-derived props using registered selectors.
Usage
function PriceDisplay( { price, currency } ) {
return new Intl.NumberFormat( 'en-US', {
style: 'currency',
currency,
} ).format( price );
}
const { withSelect } = wp.data;
const HammerPriceDisplay = withSelect( ( select, ownProps ) => {
const { getPrice } = select( 'my-shop' );
const { currency } = ownProps;
return {
price: getPrice( 'hammer', currency ),
};
} )( PriceDisplay );
// Rendered in the application:
//
// <HammerPriceDisplay currency="USD" />
In the above example, when HammerPriceDisplay is rendered into an
application, it will pass the price into the underlying PriceDisplay
component and update automatically if the price of a hammer ever changes in
the store.
Parameters
Function: Function called on every state change, expected to return object of props to merge with the component's own props.Returns
Component: Enhanced component with merged state data props.
FAQs
Data module for WordPress.
The npm package @wordpress/data receives a total of 64,463 weekly downloads. As such, @wordpress/data popularity was classified as popular.
We found that @wordpress/data demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.