Share
Embed
Transcript
60 slides
-
MY FRIEND OSCAR Meet Oscar 1. My Colleage 2. He
works with 3. Passionated about Software Development -
MY FRIEND OSCAR Meet Oscar 1. …He is not an
early morning person. -
co-IT.eu GmbH We Empower Outstanding Business Solutions “ Collect your
questions for the Q&A session, please. @GregOnNet -
AGENDA Our Review With Oscar 1. Property Pattern 2. @ngrx/entity
3. @ngrx/router-store 4. selectors 5. ngrx-data -
export function reducer(state = initialState, action: NotesActions): State { switch
(action.type) { case NotesActionTypes.CreateNoteSuccess: { return { ...state, notes: [...state.notes, action.payload], loaded: true, loading: false } } case NotesActionTypes.LoadNotesSuccess: { return { ...state, notes: ...action.payload, loaded: true, loading: false } /* ... */ Redundant Code -
export function reducer(state = initialState, action: NotesActions): State { switch
(action.type) { case NotesActionTypes.CreateNoteSuccess: { return { ...state, notes: [...state.notes, action.payload], loaded: true, loading: false } } case NotesActionTypes.LoadNotesSuccess: { return { ...state, notes: ...action.payload, loaded: true, loading: false } /* ... */ Redundant Code -
/* ... */ case NotesActionTypes.LoadAdditionalNotesSuccess: { return { ...state, notes:
[...state.notes, ...action.payload], loaded: true, loading: false } } case NotesActionTypes.DeleteSingleNoteSuccess: { return { ...state, notes: state.notes.filter(note => note.guid !== action.payload.guid), loaded: true, loading: false } } /* ... */ Remove By Filtering -
OSCAR‘S PROBLEM Large Switch-Case-Statements 1. Lot‘s of list operations we
may not need every time 2. Hard to maintain 3. Less readable -
PROPERTY PATTERN Convert Collections To Dictionaries export interface State {
notes: Note[]; } export interface State { notes: { [key: string]: Note }; } List to Object -
PROPERTY PATTERN Delete Single Object return { ...state, notes: state.notes.filter(note
=> note.guid !== action.payload.guid ) } const { [action.payload.guid]: deleted, ...withoutDeleted } = state.notes; return { ...state, notes: withoutDeleted, } -
MY FRIEND OSCAR Oscar asks… Maybe accessing data is more
efficient. But the code complexity has increased. How can we benefit from this approach? -
@ngrx/entity Entity State export interface State extends EntityState<Note> {} export
interface State<T> { ids: string[]; entities: { [id: string]: T }; } Leverages Property Pattern -
@ngrx/entity Entity Adapter import { createEntityAdapter } from '@ngrx/entity'; const
adapter = createEntityAdapter<T>(); The mighty helper -
@ngrx/entity Simplify Mutations return adapter.removeOne( action.payload, state ); const {
[action.payload.guid]: deleted, ...withoutDeleted } = state.notes; return { ...state, notes: withoutDeleted, } 1. Enusres Immutability 2. Applies State Mutation -
@ngrx/entity Entity Selectors const adapter = createEntityAdapter<T>(); export const {
selectAll, selectEntities, selectIds, selectTotal } = adapter.getSelectors(); -
@ngrx/entity Use Entity Selectors export class NotesDashboardComponent { notes$: Observable<Note[]>;
constructor(private store: Store<fromNotes.State>) { this.notes$ = this.store.pipe(select(fromNotes.selectAll)); } } -
MY FRIEND OSCAR Oscar asks… @ngrx/entity is nice, thanks. Can
we tidy up these Switch-Case-Statements now? -
CREATE REDUCER Factory Pattern To The Rescue const mutators: ActionHandlers<State>
= { [NotesActionTypes.CreateNote]: notes.addOne, [NotesActionTypes.LoadNotesSuccessful]: notes.addMany }; export function reducer(state = initialState, action) { return createReducer<State>(mutators)(state, action); } Refer to last slide for the source -
PROPERTY PATTERN Review Reduced Infrastructure Code Reducers do not need
to be enhanced as Requirements change -
MY FRIEND OSCAR Oscar asks… Small things can have a
great impact to quality. But wait since you are here… -
OSCAR‘S PROBLEM He thinks he breakse the Redux Pattern Shouldn’t
the store be able to answer every question of a Component? -
SINGLE SOURCE OF TRUTH How to deal with location state?
/* ... */ export class NoteDetailsComponent { note$: Observable<Note>; constructor( private route: ActivatedRoute, private store: Store<fromNotes.State>) { this.note$ = this.route.params.pipe( switchMap(params => this.store.pipe(state => state.notes.entities[params.guid]) ) ); } } -
@ngrx/router-store Setup import { StoreRouterConnectingModule } from '@ngrx/router-store'; @NgModule({ imports:
[ /* ... */ StoreRouterConnectingModule, ] /* ... */ }) export class AppModule {} -
@ngrx/router-store Types & Reducer Come For Free import * as
fromRouter from '@ngrx/router-store'; export interface State { routerReducer: fromRouter.RouterReducerState<RouterStateUrl>; } export const reducers: ActionReducerMap<State> = { routerReducer: fromRouter.routerReducer }; -
@ngrx/router-store Enhance The State Tree Store Notes Router State provided
by @ngrx/router-store -
@ngrx/router-store Access The Router State import { createFeatureSelector } from
'@ngrx/store'; export const getRouterState = createFeatureSelector('routerReducer'); -
@ngrx/router-store Read Router State export const currentDetails = createSelector( getEntities,
getRouterState, (notes, router) => entities[router.state.params.guid] ); RoutingComponent select -
@ngrx/router-store The Reducer‘s Outcome Let’s traverse through the whole state
tree! Of Cause Not! -
PROPERTY PATTERN Review Store is Single Source of Truth again
Reduced Complexity of Component Component does not rely on ActivatedRoute anymore -
MY FRIEND OSCAR Oscar asks… This feels more correct than
before, thanks. Wait! There is one very last thing… -
OSCAR‘S PROBLEM I Can See A Revenent Pattern…. We only
do CRUD operations. Do we need to repeat ourselves for every entity? -
Configure an entity export const entityMetadata: EntityMetadataMap = { Note:
{ selectId: (note: Note) => note.guid } }; export const pluralNames = { Note: 'Notes' }; ngrx-data -
ngrx-data Data Services import { Note } from '../../models/note'; @Injectable()
export class NotesBoard extends EntityCollectionServiceBase<Note> { constructor(entityServiceFactory: EntityCollectionServiceFactory) { super('Note', entityServiceFactory); } } -
ngrx-data Built-In Functions Of A Data Service Mutators & Selectors
for the given entity. -
PROPERTY PATTERN Review Less Files to maintain Scales good for
many entities Highly Configurable Handles Loading State automatically High Learning Curve Lot‘s of things happen behind the scenes -
co-IT.eu GmbH We Empower Outstanding Business Solutions Thank you! @GregOnNet
e.co-it.eu/dwx18-gift e.co-it.eu/dwx18-ng -
CREDITS Icons - from www.flaticon.com by Vectors Market - from
www.flaticon.com by Freepik - from www.flaticon.com by Freepik