Skip to content

a collection of best practices / commonly used patterns with ngrx extensions - store, effects, router and others

Notifications You must be signed in to change notification settings

orizens/ngrx-styleguide

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 

Repository files navigation

ngrx Style Guide

Purpose

The idea for this styleguide is to present commonly used techniques for working with ngrx suite and serve as a kind of a cookbook/recipes with a problem/solution theme.
The purpose of this style guide is to provide guidance on how to integrate ngrx-X-tool by showing the conventions used by users of the community.

Introduction Blog Post

Projects Following The Styleguide

Please open an issue to add your project/suggestion


Table of Contents

  1. Store Single Directory
  2. Creating A CoreStoreModule
  3. combining reducers
  4. using Side Effects
  5. consuming reducers in components
  6. using selectors

Store Single Directory

  • The store should be placed in the application's core directory.
  • each reducer should have a dedicated directory :
- src
  - app
    - core
      - store
        - now-playing
        - player
        - player-search
        - user-profile

Creating A CoreStoreModule

A single core store module should include:

  1. Bootstraping of the store with StoreModule.provideStore()
  2. The application's actions as providers

location: app/core/store/index.ts

Copyright (c) Oren Farhi

Back to top

About

a collection of best practices / commonly used patterns with ngrx extensions - store, effects, router and others

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •