Count: {{ count() }}
\n \n \n `\n})\nexport class CounterComponent {\n private store = inject(Store);\n \n count = createSignal((state) => state.counter?.value ?? 0);\n\n increment() {\n this.store.dispatchAction(new IncrementCounterAction(1));\n }\n\n decrement() {\n this.store.dispatchAction(new DecrementCounterAction());\n }\n}\n```\n\n loading = createSignal((state) => state.users?.loading ?? false);\n userCount = createSignal((state) => (state.users?.list ?? []).length);\n}\n```\n\n### Direct State Access\n\nAccess the current state directly:\n\n```typescript\n@Component(...)\nexport class MyComponent {\n private store = inject(Store);\n\n getCurrentState() {\n const currentState = this.store.state(); // Signal access\n }\n}\n```\n\n### Tracking Processed Actions\n\nMonitor which action was last processed:\n\n```typescript\n@Component(...)\nexport class MyComponent {\n private store = inject(Store);\n \n lastAction = createSignal((state) => this.store.processedAction().type);\n}\n```\n\n## Registering Reducers and Effects\n\n### Single Reducer/Effect\n\n```typescript\nimport { provideReducer, provideEffect } from 'ngssm-store';\n\nbootstrapApplication(AppComponent, {\n providers: [\n provideNgssmStore(),\n provideReducer(CounterReducer),\n provideEffect(UserEffect)\n ]\n});\n```\n\n### Multiple Reducers/Effects\n\n```typescript\nimport { provideReducers, provideEffects } from 'ngssm-store';\n\nbootstrapApplication(AppComponent, {\n providers: [\n provideNgssmStore(),\n provideReducers(\n CounterReducer,\n UserReducer,\n SettingsReducer\n ),\n provideEffects(\n UserEffect,\n NotificationEffect\n )\n ]\n});\n```\n\n### Effect Functions\n\nEffect functions are the modern replacement for the `Effect` interface. They are executed in an injection context, allowing you to use Angular's `inject` function for dependency injection:\n\n```typescript\nimport { provideEffectFunc } from 'ngssm-store';\nimport { inject } from '@angular/core';\n\nbootstrapApplication(AppComponent, {\n providers: [\n provideNgssmStore(),\n provideEffectFunc('LOAD_USERS', (state, action) => {\n const userService = inject(UserService);\n const dispatcher = inject(ACTION_DISPATCHER);\n \n userService.getUsers().subscribe((users) => {\n dispatcher.dispatchAction(new SetUsersAction(users));\n });\n })\n ]\n});\n```\n\nEffect functions should be preferred over the legacy `Effect` interface implementation as they are more concise and leverage Angular's dependency injection system.\n\n## Feature States\n\nOrganize state by feature for better modularity:\n\n```typescript\nimport { NgSsmFeatureState } from 'ngssm-store';\n\n@NgSsmFeatureState({\n featureStateKey: 'products',\n initialState: {\n list: [],\n loading: false,\n selectedId: null\n }\n})\nexport class ProductFeatureState {}\n\n// Access in components\nproducts = createSignal((state) => state.products?.list ?? []);\n```\n\n## State Initializers\n\nInitialize state with data from external sources:\n\n```typescript\nimport { StateInitializer } from 'ngssm-store';\n\n@Injectable()\nexport class AppInitializer implements StateInitializer {\n private configService = inject(ConfigService);\n\n initializeState(state: State): State {\n const config = this.configService.getConfig();\n return update(state, {\n settings: { $set: config }\n });\n }\n}\n\n// Provide it\nbootstrapApplication(AppComponent, {\n providers: [\n provideNgssmStore(),\n { provide: NGSSM_STATE_INITIALIZER, useClass: AppInitializer }\n ]\n});\n```\n\n## Action Processing\n\n### Sequential Processing\n\nActions are processed sequentially using an action queue:\n\n1. Action dispatched\n2. Added to queue\n3. Store schedules processing (via setTimeout by default)\n4. Reducers update state\n5. State published to all subscribers\n6. Effects process action (can dispatch new actions)\n7. Next action processed\n\n### Macro Tasks vs Micro Tasks\n\nBy default, the store uses `setTimeout` (macro-tasks) for action processing. You can switch to micro-tasks (Promises) if needed:\n\n```typescript\n@Injectable()\nexport class Store {\n // Set to false for micro-tasks (Promise.resolve())\n public useMacroTasks = true;\n}\n```\n\n## Best Practices\n\n1. **Keep Actions Simple**: Actions should be serializable plain objects\n2. **Pure Reducers**: Never mutate state directly; always use `immutability-helper`\n3. **Avoid Side Effects in Reducers**: Use Effects for side effects\n4. **Type Your State**: Define clear State interfaces\n5. **Use Signals for Performance**: Prefer `createSignal` over RxJS when possible in new code\n6. **Single Responsibility**: One reducer per feature/domain\n7. **Logging**: Use the Logger service for debugging\n8. **Action Names**: Use clear, descriptive action type names (FEATURE_ACTION_NAME pattern)\n9. **Immutability**: Never modify state objects in reducers\n10. **Error Handling**: Handle errors in effects and dispatch error actions\n\n## API Reference\n\n### Store Class\n\n- `state(): Signal