-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(storage-plugin): ensure the deserialization is not skipped for master key #1887
Conversation
BundleMonFiles updated (2)
Unchanged files (4)
Total files change -993B -0.34% Groups updated (6)
Final result: ✅ View report in BundleMon website ➡️ |
BundleMon (NGXS Plugins)Files updated (4)
Unchanged files (24)
Total files change +2.03KB +1.89% Groups updated (6)
Final result: ❌ View report in BundleMon website ➡️ |
BundleMon (Integration Projects)Files updated (4)
Total files change +1.05KB +0.38% Final result: ✅ View report in BundleMon website ➡️ |
de0a3e5
to
35e4575
Compare
Code Climate has analyzed commit 80513cf and detected 2 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 96.4% (0.1% change). View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!!!
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@ngxs/form-plugin](https://github.com/ngxs/store) | dependencies | patch | [`3.7.4` -> `3.7.5`](https://renovatebot.com/diffs/npm/@ngxs%2fform-plugin/3.7.4/3.7.5) | | [@ngxs/storage-plugin](https://github.com/ngxs/store) | dependencies | patch | [`3.7.4` -> `3.7.5`](https://renovatebot.com/diffs/npm/@ngxs%2fstorage-plugin/3.7.4/3.7.5) | | [@ngxs/store](https://github.com/ngxs/store) | dependencies | patch | [`3.7.4` -> `3.7.5`](https://renovatebot.com/diffs/npm/@ngxs%2fstore/3.7.4/3.7.5) | --- ### Release Notes <details> <summary>ngxs/store</summary> ### [`v3.7.5`](https://github.com/ngxs/store/blob/HEAD/CHANGELOG.md#​375-2022-08-08) [Compare Source](ngxs/store@v3.7.4...v3.7.5) - Performance: Tree-shake no type on the action error [#​1858](ngxs/store#1858) - Fix: Give back control to `developmentMode` config property [#​1878](ngxs/store#1878) - Fix: Do not use `refCount()` since it makes selectable stream cold [#​1883](ngxs/store#1883) - Fix: Remove `?` from `ctx` parameter of lifecycle hooks since they are never undefined [#​1889](ngxs/store#1889) - Fix: Avoid incorrectly ordered state observable events [#​1908](ngxs/store#1908) - Fix: Router Plugin - Prevent router overriding valid navigation [#​1907](ngxs/store#1907) - Fix: Storage Plugin - Provide more meaningful error message when the storage quota exceeds [#​1863](ngxs/store#1863) - Fix: Storage Plugin - Ensure the deserialization is not skipped for master key [#​1887](ngxs/store#1887) - Fix: Storage Plugin - Do not re-hydrate the whole state when the feature state is added [#​1887](ngxs/store#1887) - Fix: Devtools Plugin - Enable time-traveling for navigation actions [#​1868](ngxs/store#1868) - Fix: Form Plugin - Prevent actions infinite loop with multiple `ngxsForm` directives [#​1890](ngxs/store#1890) - Fix: Do not check if the state class is injectable within the decorator since the `ɵprov` will not exist in JIT mode [#​1867](ngxs/store#1867) - Revert: revert select decorator changes and add deprecation note [#​1871](ngxs/store#1871) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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 these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4xNTEuMiIsInVwZGF0ZWRJblZlciI6IjMyLjE1Mi4wIn0=--> Co-authored-by: cabr2-bot <[email protected]> Reviewed-on: https://codeberg.org/Calciumdibromid/CaBr2/pulls/1497 Reviewed-by: Epsilon_02 <[email protected]> Co-authored-by: Calciumdibromid Bot <[email protected]> Co-committed-by: Calciumdibromid Bot <[email protected]>
Issues: #1857 and #1146
1857: This is a follow-up fix for 2f9542d. We added a check if we need to re-hydrate the state again or not (considering
action.addedStates
). But this should never happen for the default state key (@@STATE
).1146: This is an old issue that also related to unnecessary state re-hydration when the default state key is used. We re-hydrate the whole state when any feature state is added by doing
state = { ...state, ...val }
. My fix adds some kind of "smart merge" that checks what feature state has been added and picks its name fromval
.