Skip to content

feat: support local effect registration #1

@Pierre-MarieMarchio

Description

@Pierre-MarieMarchio

Description:

Implement the ability to register effects at the feature/module level, not just globally via provideEffects in the app config. Introduce the ability to:

  • Register Effects locally within a Manager (like local Updators)
  • Use ad-hoc Effects, passed directly into a dispatch call without prior registration

This gives developers more control over scoping and use cases such as isolated features or unit testing.


Tasks:

  • registration support
    • Ensure the manager keeps track of locally registered effects
    • Ensure locally registered effects are only active for actions dispatched by that manager
  • Ad-hoc usage support
    • Ensure these effects are executed only for that call
    • They should not be globally registered or reused
  • Priority & execution order
    • If extended later, allow future options for beforeUpdator execution
  • Conflict handling
    • Conflict handling
    • Clearly define precedence and isolation rules

Expected Outcome:

  • Effects should be properly scoped to the Manager or ad-hoc usage, without interfering with global effects.
  • Developers should have a clean way to use effects only within the scope of their immediate needs, allowing more flexibility in testing and state management.

Sub-issues

Metadata

Metadata

Labels

featureNew feature or request

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions