feat: createStructuredSelector returns OutputSelector #499
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.
Hi,
unlike
createSelector
that returnsOutputSelector
, thecreateStructuredSelector
currently returns aSelector
.What is the difference?
OutputSelector
is extendedSelector
and additionally, it includes:Those are great for testing purposes. These attributes are obviously there, but it is a bit awkward to access them in TS project.
The
resultFunc
accepts the the input selectors in somewhat unknown order, becauseObject.keys
does not guarantee to return the same values in the same order in all environments. Thus the arguments ofresultFunc
in this PR are justany
. Nonetheless e.g.recomputations
are easily accessible.