上一篇:ngRx 官方示例分析 - 2. Action 管理

这里我们讨论 reducer.

如果你注意的话,会看到在不同的 Action 定义文件中,导出的 Action 类型名称都是 Actions ,在导入的时候,同时导入同名的类型就是问题了。这里首先使用了 import as 语法进行重命名。

import * as book from '../actions/book';
import * as collection from '../actions/collection';

这样我们就可以区分来自不同定义文件的 Actions 了。

对于每个 reducer  来说,状态虽然一直在变,但是所管理的状态的基本的结构是不变的,我们通过接口进行约束。

比如 Book,我们定义如下状态的接口。注意这个接口的名称没有 Book,是统一的 State,在导入这个定义的时候,使用  import as 语法进行重命名。

export interface State {
ids: string[];
entities: { [id: string]: Book };
selectedBookId: string | null;
};

Book 的初始状态当然需要实现这个接口的。

export const initialState: State = {
ids: [],
entities: {},
selectedBookId: null,
};

辅助函数

在 Reducer 中提供了辅助函数,以便于数据访问。

/**
* Because the data structure is defined within the reducer it is optimal to
* locate our selector functions at this level. If store is to be thought of
* as a database, and reducers the tables, selectors can be considered the
* queries into said database. Remember to keep your selectors small and
* focused so they can be combined and composed to fit each particular
* use-case.
*/ export const getEntities = (state: State) => state.entities; export const getIds = (state: State) => state.ids; export const getSelectedId = (state: State) => state.selectedBookId; export const getSelected = createSelector(getEntities, getSelectedId, (entities, selectedId) => {
return entities[selectedId];
}); export const getAll = createSelector(getEntities, getIds, (entities, ids) => {
return ids.map(id => entities[id]);
});

这个 createSelector 函数来自 reselect

Simple “selector” library for Redux inspired by getters in NuclearJSsubscriptions in re-frame and this proposal from speedskater.

  • Selectors can compute derived data, allowing Redux to store the minimal possible state.
  • Selectors are efficient. A selector is not recomputed unless one of its arguments change.
  • Selectors are composable. They can be used as input to other selectors.

需要注意的是,Book 有 4 个 Action 的定义,

  • Search
  • SearchComplete
  • Load
  • Select

在 Book 的处理中并没有 SearchAction 的处理。它需要我们发出一个异步的请求,在 @ngrx 中,它需要 @ngrx/effect 来处理,

源代码

下面是 Book 的 reducer 的全部代码。/app/reducers/books.ts

import { createSelector } from 'reselect';
import { Book } from '../models/book';
import * as book from '../actions/book';
import * as collection from '../actions/collection'; export interface State {
ids: string[];
entities: { [id: string]: Book };
selectedBookId: string | null;
}; export const initialState: State = {
ids: [],
entities: {},
selectedBookId: null,
}; export function reducer(state = initialState, action: book.Actions | collection.Actions): State {
switch (action.type) {
case book.ActionTypes.SEARCH_COMPLETE:
case collection.ActionTypes.LOAD_SUCCESS: {
const books = action.payload;
const newBooks = books.filter(book => !state.entities[book.id]); const newBookIds = newBooks.map(book => book.id);
const newBookEntities = newBooks.reduce((entities: { [id: string]: Book }, book: Book) => {
return Object.assign(entities, {
[book.id]: book
});
}, {}); return {
ids: [ ...state.ids, ...newBookIds ],
entities: Object.assign({}, state.entities, newBookEntities),
selectedBookId: state.selectedBookId
};
} case book.ActionTypes.LOAD: {
const book = action.payload; if (state.ids.indexOf(book.id) > -1) {
return state;
} return {
ids: [ ...state.ids, book.id ],
entities: Object.assign({}, state.entities, {
[book.id]: book
}),
selectedBookId: state.selectedBookId
};
} case book.ActionTypes.SELECT: {
return {
ids: state.ids,
entities: state.entities,
selectedBookId: action.payload
};
} default: {
return state;
}
}
} /**
* Because the data structure is defined within the reducer it is optimal to
* locate our selector functions at this level. If store is to be thought of
* as a database, and reducers the tables, selectors can be considered the
* queries into said database. Remember to keep your selectors small and
* focused so they can be combined and composed to fit each particular
* use-case.
*/ export const getEntities = (state: State) => state.entities; export const getIds = (state: State) => state.ids; export const getSelectedId = (state: State) => state.selectedBookId; export const getSelected = createSelector(getEntities, getSelectedId, (entities, selectedId) => {
return entities[selectedId];
}); export const getAll = createSelector(getEntities, getIds, (entities, ids) => {
return ids.map(id => entities[id]);
});

/app/reducers/collection.ts

import * as collection from '../actions/collection';

export interface State {
loaded: boolean;
loading: boolean;
ids: string[];
}; const initialState: State = {
loaded: false,
loading: false,
ids: []
}; export function reducer(state = initialState, action: collection.Actions): State {
switch (action.type) {
case collection.ActionTypes.LOAD: {
return Object.assign({}, state, {
loading: true
});
} case collection.ActionTypes.LOAD_SUCCESS: {
const books = action.payload; return {
loaded: true,
loading: false,
ids: books.map(book => book.id)
};
} case collection.ActionTypes.ADD_BOOK_SUCCESS:
case collection.ActionTypes.REMOVE_BOOK_FAIL: {
const book = action.payload; if (state.ids.indexOf(book.id) > -1) {
return state;
} return Object.assign({}, state, {
ids: [ ...state.ids, book.id ]
});
} case collection.ActionTypes.REMOVE_BOOK_SUCCESS:
case collection.ActionTypes.ADD_BOOK_FAIL: {
const book = action.payload; return Object.assign({}, state, {
ids: state.ids.filter(id => id !== book.id)
});
} default: {
return state;
}
}
} export const getLoaded = (state: State) => state.loaded; export const getLoading = (state: State) => state.loading; export const getIds = (state: State) => state.ids;

/app/reducers/layout.ts

import * as layout from '../actions/layout';

export interface State {
showSidenav: boolean;
} const initialState: State = {
showSidenav: false,
}; export function reducer(state = initialState, action: layout.Actions): State {
switch (action.type) {
case layout.ActionTypes.CLOSE_SIDENAV:
return {
showSidenav: false
}; case layout.ActionTypes.OPEN_SIDENAV:
return {
showSidenav: true
}; default:
return state;
}
} export const getShowSidenav = (state: State) => state.showSidenav;

/app/reducers/search.ts

import * as book from '../actions/book';

export interface State {
ids: string[];
loading: boolean;
query: string;
}; const initialState: State = {
ids: [],
loading: false,
query: ''
}; export function reducer(state = initialState, action: book.Actions): State {
switch (action.type) {
case book.ActionTypes.SEARCH: {
const query = action.payload; if (query === '') {
return {
ids: [],
loading: false,
query
};
} return Object.assign({}, state, {
query,
loading: true
});
} case book.ActionTypes.SEARCH_COMPLETE: {
const books = action.payload; return {
ids: books.map(book => book.id),
loading: false,
query: state.query
};
} default: {
return state;
}
}
} export const getIds = (state: State) => state.ids; export const getQuery = (state: State) => state.query; export const getLoading = (state: State) => state.loading;

管理 Recuders

组合器

compose 函数用来将一组函数组合成单个单个函数。

/**
* The compose function is one of our most handy tools. In basic terms, you give
* it any number of functions and it returns a function. This new function
* takes a value and chains it through every composed function, returning
* the output.
*
* More: https://drboolean.gitbooks.io/mostly-adequate-guide/content/ch5.html*/
import { compose } from '@ngrx/core/compose';

ngrx-store-freeze

@ngrx/store meta reducer that prevents state from being mutated. When mutation occurs, an exception will be thrown. This is useful during development mode to ensure that no part of the app accidentally mutates the state. Ported from redux-freeze

/**
* storeFreeze prevents state from being mutated. When mutation occurs, an
* exception will be thrown. This is useful during development mode to
* ensure that none of the reducers accidentally mutates the state.
*/
import { storeFreeze } from 'ngrx-store-freeze';

combineReducers

随着应用变得复杂,需要对 reducer 函数 进行拆分,拆分后的每一块独立负责管理 state 的一部分。

combineReducers 辅助函数的作用是,把一个由多个不同 reducer 函数作为 value 的 object,合并成一个最终的 reducer 函数,然后就可以对这个 reducer 调用 createStore

合并后的 reducer 可以调用各个子 reducer,并把它们的结果合并成一个 state 对象。state 对象的结构由传入的多个 reducer 的 key 决定

通过为传入对象的 reducer 命名不同来控制 state key 的命名。例如,你可以调用 combineReducers({todos: myTodosReducer, counter: myCounterReducer }) 将 state 结构变为 { todos, counter }

通常的做法是命名 reducer,然后 state 再去分割那些信息,因此你可以使用 ES6 的简写方法:combineReducers({ counter, todos })。这与 combineReducers({ counter: counter, todos: todos })一样。

http://www.redux.org.cn/docs/api/combineReducers.html

/**
* combineReducers is another useful metareducer that takes a map of reducer
* functions and creates a new reducer that stores the gathers the values
* of each reducer and stores them using the reducer's key. Think of it
* almost like a database, where every reducer is a table in the db.
*
* More: https://egghead.io/lessons/javascript-redux-implementing-combinereducers-from-scratch*/
import { combineReducers } from '@ngrx/store';

组合 Recuders

这是函数式编程中的方法,为了方便,被放到了 Redux 里。 当需要把多个 store 增强器 依次执行的时候,需要用到它。

http://www.redux.org.cn/docs/api/compose.html

将各个状态和 reducer 组合为单个的 reducer。

/**
* As mentioned, we treat each reducer like a table in a database. This means
* our top level state interface is just a map of keys to inner state types.
*/
export interface State {
search: fromSearch.State;
books: fromBooks.State;
collection: fromCollection.State;
layout: fromLayout.State;
router: fromRouter.RouterState;
} /**
* Because metareducers take a reducer function and return a new reducer,
* we can use our compose helper to chain them together. Here we are
* using combineReducers to make our top level reducer, and then
* wrapping that in storeLogger. Remember that compose applies
* the result from right to left.
*/
const reducers = {
search: fromSearch.reducer,
books: fromBooks.reducer,
collection: fromCollection.reducer,
layout: fromLayout.reducer,
router: fromRouter.routerReducer,
}; const developmentReducer: ActionReducer<State> = compose(storeFreeze, combineReducers)(reducers);
const productionReducer: ActionReducer<State> = combineReducers(reducers);

在 compose 的时候,已经传递了当前的 reducers .

最后导出了 reducer 函数

export function reducer(state: any, action: any) {
if (environment.production) {
return productionReducer(state, action);
} else {
return developmentReducer(state, action);
}
}

注册 reducer

在 /app/app.module.ts 中,注册到 store 中。注意 './reducers' 实际上导入的是 /app/reducers/index.ts。

import { reducer } from './reducers';

    /**
* StoreModule.provideStore is imported once in the root module, accepting a reducer
* function or object map of reducer functions. If passed an object of
* reducers, combineReducers will be run creating your application
* meta-reducer. This returns all providers for an @ngrx/store
* based application.
*/
StoreModule.provideStore(reducer),

一些辅助函数

获取当前图书列表的辅助函数。

export const getBooksState = (state: State) => state.books;

源码

在 /app/reducers/index.ts 中,

import { createSelector } from 'reselect';
import { ActionReducer } from '@ngrx/store';
import * as fromRouter from '@ngrx/router-store';
import { environment } from '../../environments/environment'; /**
* The compose function is one of our most handy tools. In basic terms, you give
* it any number of functions and it returns a function. This new function
* takes a value and chains it through every composed function, returning
* the output.
*
* More: https://drboolean.gitbooks.io/mostly-adequate-guide/content/ch5.html
*/
import { compose } from '@ngrx/core/compose'; /**
* storeFreeze prevents state from being mutated. When mutation occurs, an
* exception will be thrown. This is useful during development mode to
* ensure that none of the reducers accidentally mutates the state.
*/
import { storeFreeze } from 'ngrx-store-freeze'; /**
* combineReducers is another useful metareducer that takes a map of reducer
* functions and creates a new reducer that stores the gathers the values
* of each reducer and stores them using the reducer's key. Think of it
* almost like a database, where every reducer is a table in the db.
*
* More: https://egghead.io/lessons/javascript-redux-implementing-combinereducers-from-scratch
*/
import { combineReducers } from '@ngrx/store'; /**
* Every reducer module's default export is the reducer function itself. In
* addition, each module should export a type or interface that describes
* the state of the reducer plus any selector functions. The `* as`
* notation packages up all of the exports into a single object.
*/
import * as fromSearch from './search';
import * as fromBooks from './books';
import * as fromCollection from './collection';
import * as fromLayout from './layout'; /**
* As mentioned, we treat each reducer like a table in a database. This means
* our top level state interface is just a map of keys to inner state types.
*/
export interface State {
search: fromSearch.State;
books: fromBooks.State;
collection: fromCollection.State;
layout: fromLayout.State;
router: fromRouter.RouterState;
} /**
* Because metareducers take a reducer function and return a new reducer,
* we can use our compose helper to chain them together. Here we are
* using combineReducers to make our top level reducer, and then
* wrapping that in storeLogger. Remember that compose applies
* the result from right to left.
*/
const reducers = {
search: fromSearch.reducer,
books: fromBooks.reducer,
collection: fromCollection.reducer,
layout: fromLayout.reducer,
router: fromRouter.routerReducer,
}; const developmentReducer: ActionReducer<State> = compose(storeFreeze, combineReducers)(reducers);
const productionReducer: ActionReducer<State> = combineReducers(reducers); export function reducer(state: any, action: any) {
if (environment.production) {
return productionReducer(state, action);
} else {
return developmentReducer(state, action);
}
} /**
* A selector function is a map function factory. We pass it parameters and it
* returns a function that maps from the larger state tree into a smaller
* piece of state. This selector simply selects the `books` state.
*
* Selectors are used with the `select` operator.
*
* ```ts
* class MyComponent {
* constructor(state$: Observable<State>) {
* this.booksState$ = state$.select(getBooksState);
* }
* }
* ```
*/
export const getBooksState = (state: State) => state.books; /**
* Every reducer module exports selector functions, however child reducers
* have no knowledge of the overall state tree. To make them useable, we
* need to make new selectors that wrap them.
*
* The createSelector function from the reselect library creates
* very efficient selectors that are memoized and only recompute when arguments change.
* The created selectors can also be composed together to select different
* pieces of state.
*/
export const getBookEntities = createSelector(getBooksState, fromBooks.getEntities);
export const getBookIds = createSelector(getBooksState, fromBooks.getIds);
export const getSelectedBookId = createSelector(getBooksState, fromBooks.getSelectedId);
export const getSelectedBook = createSelector(getBooksState, fromBooks.getSelected); /**
* Just like with the books selectors, we also have to compose the search
* reducer's and collection reducer's selectors.
*/
export const getSearchState = (state: State) => state.search; export const getSearchBookIds = createSelector(getSearchState, fromSearch.getIds);
export const getSearchQuery = createSelector(getSearchState, fromSearch.getQuery);
export const getSearchLoading = createSelector(getSearchState, fromSearch.getLoading); /**
* Some selector functions create joins across parts of state. This selector
* composes the search result IDs to return an array of books in the store.
*/
export const getSearchResults = createSelector(getBookEntities, getSearchBookIds, (books, searchIds) => {
return searchIds.map(id => books[id]);
}); export const getCollectionState = (state: State) => state.collection; export const getCollectionLoaded = createSelector(getCollectionState, fromCollection.getLoaded);
export const getCollectionLoading = createSelector(getCollectionState, fromCollection.getLoading);
export const getCollectionBookIds = createSelector(getCollectionState, fromCollection.getIds); export const getBookCollection = createSelector(getBookEntities, getCollectionBookIds, (entities, ids) => {
return ids.map(id => entities[id]);
}); export const isSelectedBookInCollection = createSelector(getCollectionBookIds, getSelectedBookId, (ids, selected) => {
return ids.indexOf(selected) > -1;
}); /**
* Layout Reducers
*/
export const getLayoutState = (state: State) => state.layout; export const getShowSidenav = createSelector(getLayoutState, fromLayout.getShowSidenav);

总结

通过 Reducer 建立对 store 状态的维护,示例中还提供了一些辅助函数来帮助简化数据访问。

参考资源:

ngRx 官方示例分析 - 3. reducers的更多相关文章

  1. ngRx 官方示例分析 - 2. Action 管理

    我们从 Action 名称开始. 解决 Action 名称冲突问题 在 ngRx 中,不同的 Action 需要一个 Action Type 进行区分,一般来说,这个 Action Type 是一个字 ...

  2. ngRx 官方示例分析 - 1. 介绍

    ngRx 的官方示例演示了在具体的场景中,如何使用 ngRx 管理应用的状态. 示例介绍 示例允许用户通过查询 google 的 book  API  来查询图书,并保存自己的精选书籍列表. 菜单有两 ...

  3. ngRx 官方示例分析 - 4.pages

    Page 中通过构造函数注入 Store,基于 Store 进行数据操作. 注意 Component 使用了 changeDetection: ChangeDetectionStrategy.OnPu ...

  4. ngRx 官方示例分析 - 6 - Effect

    @ngrx/effect 前面我们提到,在 Book 的 reducer 中,并没有 Search 这个 Action 的处理,由于它需要发出一个异步的请求,等到请求返回前端,我们需要根据返回的结果来 ...

  5. ngRx 官方示例分析 - 5. components

    组件通过标准的 Input 和 Output 进行操作,并不直接访问 store. /app/components/book-authors.ts import { Component, Input ...

  6. RocketMQ源码分析之从官方示例窥探:RocketMQ事务消息实现基本思想

    摘要: RocketMQ源码分析之从官方示例窥探RocketMQ事务消息实现基本思想. 在阅读本文前,若您对RocketMQ技术感兴趣,请加入RocketMQ技术交流群 RocketMQ4.3.0版本 ...

  7. Halcon斑点分析官方示例讲解

    官方示例中有许多很好的例子可以帮助大家理解和学习Halcon,下面举几个经典的斑点分析例子讲解一下 Crystals 图中显示了在高层大气中采集到的晶体样本的图像.任务是分析对象以确定特定形状的频率. ...

  8. DotNetBar for Windows Forms 12.7.0.10_冰河之刃重打包版原创发布-带官方示例程序版

    关于 DotNetBar for Windows Forms 12.7.0.10_冰河之刃重打包版 --------------------11.8.0.8_冰河之刃重打包版------------- ...

  9. DotNetBar for Windows Forms 12.5.0.2_冰河之刃重打包版原创发布-带官方示例程序版

    关于 DotNetBar for Windows Forms 12.5.0.2_冰河之刃重打包版 --------------------11.8.0.8_冰河之刃重打包版-------------- ...

随机推荐

  1. JavaScript学习点滴 call、apply的区别

    对于apply和call两者在作用上是相同的,但两者在参数上有区别的.     1.call call 方法 调用一个对象的一个方法,以另一个对象替换当前对象. call([thisObj[,arg1 ...

  2. java.lang.Exception: 资源处理失败,失败原因:com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column '?????‰' in 'where clause'

    1:Unknown column '?????‰' in 'where clause',这个问题,百度一搜,挺多的,但是貌似好像没有解决我的问题.贴一下我是如何拼接sql的.解决这个sql拼接bug的 ...

  3. unisound_asr 云知声 语音识别 python版接口

    抽空,实现了一份云知声 语音转写的python版本. 使用python通过调用动态库实现. 云知声官网: http://dev.hivoice.cn/sdk_download/schema_sdk.j ...

  4. slave延迟很大优化方法

    一般而言,slave相对master延迟较大,其根本原因就是slave上的复制线程没办法真正做到并发.简单说,在master上是并发模式(以InnoDB引擎为主)完成事务提交的,而在slave上,复制 ...

  5. C/C++知识点清单02-上

    第二章 预处理.const.static与sizeof (上) 在这章编写时,发现了一个不错的帖子.其中对程序预处理语句的基本概念写得还是十分清晰的. (http://www.runoob.com/c ...

  6. React Native学习(一)——搭建开发环境

    第一次接触React Native,首先搭建环境,过程还算顺利,不过也遇到了些问题,这里简单记录下来.中文官网(http://reactnative.cn/docs/0.47/getting-star ...

  7. 设备树的interrupt

    http://www.cnblogs.com/targethero/p/5080499.html https://www.cnblogs.com/xiaojiang1025/p/6131381.htm ...

  8. Elixir的Phoenix框架:请求处理之道

    本文基于Phoenix1.3,但请求的处理流程跟1.2基本一致,只是模块的命名和目录结构有所差异. 简单介绍,phoenix是一个网站框架,本质就是http请求处理.这篇文章主要就是讲一个请求,在结果 ...

  9. Java想要学到精通,这几点一定要掌握

    时代更新换代速度如此之快,尤其是深处互联网行业的java程序员,技术更需要不断更新,只有及时充电,才能不被市场淘汰.千锋Java培训老师今天为大家分享Java程序员学习的6个小技巧. 1.书籍永远是知 ...

  10. python实现简单函数发生器

    最近学校又抽风把我自动化系的苦逼童鞋留下做课设,简直无聊到爆的-->用VB实现函数发生器,(语言不限制) 大伙不知从哪搞来的MATLAB版本,于是几十个人就在这基础上修修改改蒙混过关了,可我实在 ...