This repository was archived by the owner on Apr 8, 2020. It is now read-only.
redux template: automatically infer FetchData's new props type #1250
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.
After being connected to redux's store the props type isn't the same anymore since
WeatherForecastsState
gets filled by the store.The template worked because when using the
FetchData
component within theRoute
component it seems like its type doesn't get checked accurately. However using the component as<FetchData ... />
generates an error since the properties ofWeatherForecastsState
were seemingly missing.The type definition of redux's
connect
has been built in such a way, that the new props type gets automatically infered.