feat: convert entity and router selectors interfaces to types #3853
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Interfaces
EntitySelectors
andRouterStateSelectors
are not compatible withRecord<string, Selector>
which is expected ascreateSelector.extraSelectors
result. For example, we cannot add entity selectors to a specific feature in the following way:Workaround:
What is the new behavior?
Types
EntitySelectors
andRouterStateSelectors
are compatible withRecord<string, Selector>
and there is no compilation error in the example above.Does this PR introduce a breaking change?