angular-ngrx-patterns

To enforce NgRx consistency, align new code with the project's established NgRx implementation patterns. This approach inspects existing actions, reducers, effects, selectors, and facades to prevent architectural drift while extending functionality.

Architectural drift in NgRx occurs when developers introduce incompatible paradigms or fragmented styles. You avoid it by inspecting existing NgRx patterns, such as createReducer or centralized selectors, and mirroring that prevailing style for new features.

To modify NgRx actions, reducers, and effects without disruption, model changes around the project's existing implementation. This ensures new code mirrors the established style, like switch(action.type) or entity adapters, maintaining consistency and reducing fragmentation.

Yes, this approach works with both modern createReducer syntax and traditional switch statements. It inspects your specific NgRx codebase to identify the prevailing style and provides non-disruptive guidance to mirror that exact pattern for consistency.

You should not introduce new NgRx paradigms when your project already has an established state management style. Prioritizing consistency over new patterns prevents fragmentation, ensuring actions, reducers, effects, selectors, and facades remain unified.