Docs update: recommend unknown
instead of null
as ThunkAction extraArgument type
#3693
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.
Currently, the docs suggest
null
as type for theextraArgument
generic argument ofThunkAction
.This only works if the
ThunkMiddleware
is invoked withnull
asextraArgument
as well. The default value forThunkMiddleware
isunknown
though, making these thunks incompatible with the default-typedThunkMiddleware
.This change suggests to use
unknown
instead, which would work with Middlewares typed for any type ofextraArgument
.