-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Effects: Introduce Standalone API for NgRx Effects #3522
Comments
I don't know if there is an existing type we can use, but if possible we should have types in place that prevent these provider functions to be added to Component providers where they won't register correctly. |
Good idea! The The name |
I like that idea |
provideEffects
function
Information
provideEffects
function should have the same behavior asEffectsModule.forRoot
andEffectsModule.forFeature
methods, but it should provide a "module-free" developer experience. This function should have the same signature asEffectsModule
methods - it should accept an array of effect source classes.Related discussion: #3399
Describe any alternatives/workarounds you're currently using
To provide effects with standalone Angular features, we can use
importProvidersFrom
function:The
provideEffects
function should replace bothEffectsModule
methods, so it can be used in the following way:Unlike
EffectsModule.forRoot
, it won't be required to callprovideEffects
at the root level, if there are no root effects.I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: