Extension Points

Work in progress

The ngrx-data library strives for the "it just works" experience. But customizations are an inevitable necessity.

The ngrx-data library invites you to customize its behavior at many points, most of them listed here.

Take control of an entity type

One day you decide that a particular entity type needs special treatment. You want to take over some or all of the management of that type.

You can do that easily without abandoning ngrx-data for the rest of your entity model.

You can take it over completely simply by removing it from the entity metadata. Create your own collection and add it to the store's state-tree as you would in vanilla ngrx. Create your own actions, reducers, selectors and effects. As long as your actions don't have an entityName or op property, ngrx-data will ignore them.

Or you can keep the entity type in the ngrx-data system and take over the behaviors that matter to you.

• Create supplemental actions for that type. Give them custom op names that suit your purpose.

• Register an alternative EntityCollectionReducer for that type with the EntityReducerFactory. Your custom reducer can respond to your custom actions and implement the standard operations in its own way.

• Create your own service facade, an alternative to EntityCollectionService, that dispatches the actions you care about and exposes the selectors that your type needs.

• Add additional properties to the collection state with the EntityMetadata.additionalCollectionState property. Manage these properties with custom reducer actions and selectors.

• By-pass the EntityEffects completely by never dispatching an action with an op that it intercepts. Create a custom ngrx/effect that handles your custom persistence actions.

Provide alternative service implementations

The ngrx-data library consists of many services that perform small tasks.

Look at the many providers in ngrx-data.module.ts. Provide your own version of any ngrx-data service, as long as it conforms to the service API and implements the expected behavior.

Be sure to test your alternatives.

Custom EntityCollectionService

Extend the EntityCollection

Custom EntityActions

Rename the generated entity action type

The EntityActionFactory.create() method relies on the formatActionType() method to produce the Action.type string.

The default implementation concatenates the entity type name with the EntityOp. For example, querying all heroes results in the entity type, [Hero] ngrx-data/query-all.

If you don't like that approach you can replace the formatActionType() method with a generator that produces action type names that are more to your liking. The ngrx-data library doesn't make decisions based on the Action.type.

Custom EntityDispatcher

Change the default save strategy

The dispatcher's add(), update(), delete() methods dispatch optimistic or pessimistic save actions based on settings in the EntityDispatcherOptions.

These options come from the EntityDispatcherFactory that creates the dispatcher. This factory gets the options from the entity's metadata. But where the metadata lack options, the factory relies on its defaultDispatcherOptions.

You can set these default options directly by injecting the EntityDispatcherFactory and re-setting defaultDispatcherOptions before creating dispatchers (or creating an EntityCollectionService which creates a dispatcher).

Custom effects

The ngrx-data library has one ngrx @Effect, the EntityEffects class.

This class detects entity persistence actions, performs the persistence operation with a call to an EntityDataService and channels the HTTP response through a PersistenceResultHandler which produces a persistence results observable that goes back to the ngrx store.

The EntityEffects class intercepts actions that have an op property whose value is one of the persistOps. Other actions are ignored by this effect.

It tries to process any action with such an op property by looking for a

Choose data service for the type

The Entity DataService describes the default service, how to provide a data service for a specific entity type or replace the default service entirely.

Replace the generic-type effects

Handle effect for a specific type

Replace handling of the results of a data service call

Replace the EntityEffects entirely

Custom Reducers

The Entity Reducer guide explains how to customize entity reducers.

Custom data service

Replace the generic-type data service

Replace the data service for a specific type

Custom HTTP resource URLs

Add plurals

Replace the Pluralizer

Replace the HttpUrlGenerator

Serialization with back-end

The shape of the JSON data going over the wire to-and-from the server often doesn't match the shape of the entity model(s) in the client application. You may need serialization/deserialization transformation functions to map between the client entity data and the formats expected by the web APIs.

There are no facilities for this within ngrx-data itself although that is a limitation we might address in a future version.

One option in the interim is to write such serialization functions and inject them into the HttpClient pipeline with HttpClient interceptors.