fix(store): do not inject container state by default #2117
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit updates the
injectContainerState
configuration property to default to false. This change will affect the behavior of@Selector()
s, as they will no longer receive the container state as the first argument if there are any selectors in the list.The current behavior is as follows:
You might notice that the
getUnreadTotal
selector will have the notifications state injected as the first argument before accessing the notifications list.This update has been made to prevent injecting the container state as the first argument if there are any selectors provided in the
@Selector([...])
decorator. However, this change does not affect the@Selector()
decorator with no arguments.