chore(deps): update dependency react-redux to v8.0.5 #202
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.
This PR contains the following updates:
8.0.2
->8.0.5
Release Notes
reduxjs/react-redux
v8.0.5
Compare Source
This release fixes a few minor TS issues.
What's Changed
Provider
: pass state (S
) generic through toProviderProps
by @OliverJAsh in https://github.com/reduxjs/react-redux/pull/1960equalityFn
type inNoInfer
by @phryneas in https://github.com/reduxjs/react-redux/pull/1965Full Changelog: reduxjs/react-redux@v8.0.4...v8.0.5
v8.0.4
Compare Source
This patch release fixes some minor TS types issues, and updates the rarely-used
areStatesEqual
option forconnect
to now pass throughownProps
for additional use in determining which pieces of state to compare if desired.Changelog
TS Fixes
We've fixed an import of
React
that caused issues with theallowSyntheticDefaultImports
TS compiler flag in user projects.connect
already accepted a custom context instance asprops.context
, and had runtime checks in case users were passing through a real value with app data asprops.context
instead. However, the TS types did not handle that case, and this would fail to compile. If your own component expectsprops.context
with actual data,connect
's types now use that type instead.The
ConnectedProps<T>
type had a mismatch with React's built-inReact.ComponentProps<Component>
type, and that should now work correctly.Other Changes
The
areStatesEqual
option toconnect
now receivesownProps
as well, in case you need to make a more specific comparison with certain sections of state.The new signature is:
What's Changed
ComponentProps
from older@types/react
by @Andarist in https://github.com/reduxjs/react-redux/pull/1956Full Changelog: reduxjs/react-redux@v8.0.2...v8.0.4
v8.0.3
Compare Source
This release was accidentally published without an intended fix - please use v8.0.4 instead
Configuration
📅 Schedule: Branch creation - "on Friday" in timezone America/Indianapolis, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.