Better typings, No more generic Function
type. User's can specify input and output types.
#13
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.
Over at the redux-starter-kit repo which uses this lib, we are planning to switch to Typescript but the generic
Function
type selectorsselectorator
returns break type safety, so I decided to either switch toreselect
or help you guys with better typings.So basically this update allows Users to supply Input & Output type parameters. Even without those it will try to infer the output type from the getComputedValue function.
Also overloads were added to handle different parameters,
For selectors taking multiple parameters the Input type can be an array
e.g
will give the selector this type signature
Examples