Skip to main content
100%

A Comprehensive Introduction to @ngrx/store - Companion to Egghead.io Series

✓ Published0🌍 Public
Aackuser
Last edited Feb 8, 2019
Created on Jan 9, 2020

This example demonstrates the core concepts of @ngrx/store, a state management library for Angular built on RxJS. It explains the roles of reducers, actions, and the single application store, showing how immutable state flows through a centralized dispatcher and BehaviorSubject. The code highlights APIs such as `scan` for aggregating state, `map` for slicing state, `distinctUntilChanged` for managing updates, and `combineLatest` with `withLatestFrom` for projecting state into views. The accompanying walkthrough applies these patterns to a sample application, including middleware, meta-reducers, and state rehydration on bootstrap.

AI-generated description

Similar vizzes

Loading thumbnail…

Redux without the sanity checks in a single file. Don't use this, use normal Redux. :-)

This example demonstrates a minimal, single-file implementation of Redux’s core API, including `createStore`, `combineReducers`, `bindActionCreators`, and `applyMiddleware`. It shows how these functions work together to manage state and dispatch actions, with `subscribe` for listener registration and `replaceReducer` for hot-swapping. The code defines the store’s logic directly, using plain JavaScript functions like `mapValues` and `compose` to replicate the original library’s behavior without its validation checks. The listing is a gist by Stroked, intended as a concise educational reference for Redux’s internals.

AAjayyy
72% match
Loading thumbnail…

Gist 7dc4898b7ffc460291957e8784871131

This example demonstrates a React application that integrates Redux for state management with asynchronous actions via Redux Thunk. It sets up a centralized store using `createStore`, applies the `thunk` middleware, and connects the app through a `Provider` component. The root component is rendered into the DOM with `react-dom`’s `render` method, using `window.__REDUX_DEVTOOLS_EXTENSION__` for debugging. The code shows how to wire together React, Redux, and Redux Thunk, though it does not display any visual data or charting logic, focusing solely on the application’s foundational architecture.

Aamortka
71% match
Loading thumbnail…

Redux without the sanity checks in a single file. Don't use this, use normal Redux. :-)

This example presents a single-file implementation of Redux, stripped of its typical validation and sanity checks. It defines core Redux APIs, including `createStore`, `combineReducers`, `bindActionCreators`, `compose`, and `applyMiddleware`, using helper functions like `mapValues` and `pick`. The code demonstrates a minimal store with `dispatch`, `subscribe`, `getState`, and `replaceReducer` methods, initializing state with an `@@redux/INIT` action. It shows a functional, albeit simplified, version of Redux’s state management pattern, intended for educational purposes rather than production use.

RRestuta
70% match
Loading thumbnail…

Gist 7e25cbcd7c60d58ca2949795d215284a

This example illustrates four distinct approaches to reacting to a state change in an Angular application, using the RxJS `filter` and `take` operators within a `store` service. It shows how to implement a save action by observing `saveButtonState`, then demonstrates wrapping the same observable logic in a Promise for async handling, and finally presents simpler alternatives using a callback and an event emitter. The code relies on `ButtonState` enums and a `saveDone` event emitter, with no external visualization libraries or data sources involved.

HHypercubed
68% match
Loading thumbnail…

Action, reducer and store drills

This example demonstrates how to visualize Redux state management through interactive “drill” views. It shows a live, force-directed graph of actions, reducers, and store state, with nodes and links updating in real time as actions dispatch. The visualization uses `d3.forceSimulation` for layout and `d3.select` with data joins to render transitions. A CRUD reducer example (from the Glitch project “tulip-buffet”) provides the underlying state logic, while a second file (gistfile1.txt) defines internationalization (i18n) state for language-specific labels. The code wires Redux store subscriptions to D3 updates, animating node positions via `transition.attrTween`.

Aarcox80
68% match
Loading thumbnail…

redux-scc-v1-blog-example-store

This example demonstrates a Redux store chunk that manages both string and numeric-array state through generated reducers and selectors. It uses the `buildStoreChunk` helper to define a `stringReducer` and `arrayReducer` via `Types.reducer`, with `Types.string()` and `Types.arrayOf(Types.number())` schemas. The store is assembled with `createStore` and `combineReducers` from Redux, while `actions`, `reducers`, and `selectors` are destructured from the chunk configuration. The code shows a programmatic approach to structuring Redux state management without explicit action creators or reducer bodies.

TTheComfyChair
67% match
Loading thumbnail…

Gist 2d9a9b974fd730e3cd4c1dd15a66721b

This example shows a React Native application shell that wires together a Redux store, a layout component, and an application navigator. The code defines a `LargeApp` class component that renders a `<Provider>` from React Redux, passing `myStore` to wrap a `<Layout>` containing an `<ApplicationNavigator>`. It demonstrates the standard composition pattern for initializing a Redux-connected navigation hierarchy in a React Native app, using the `Component` API from React and the `Provider` component from `react-redux`. No data visualization or charting logic is present; the focus is on application bootstrapping and state management architecture.

Aanosikeosifo
67% match
Loading thumbnail…

Gist 0377e5f0142844927575a50b922f67ed

This example shows a Redux state-management structure that combines reducers for event data, explore data, and navigation data into a single root reducer. The code uses the `combineReducers` API from the Redux library to merge three feature-specific reducers—imported from `features/events/reducers`, `features/explore/reducers`, and `navigation/reducers`—into one exported object. It does not render any visualization directly; instead, it defines the data-flow backbone that organizes state for an application, likely feeding charts or maps that consume these event, exploration, and navigation datasets. The source is a gist authored by anosikeosifo.

Aanosikeosifo
67% match