Closed arturovt closed 1 month ago
CI is running/has finished running commands for commit b2b3a9720c072416360edc153aa414e1a808c92c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this CI Pipeline Execution
Sent with 💌 from NxCloud.
``` yarn add https://pkg.pr.new/@ngxs/devtools-plugin@2231.tgz ```
``` yarn add https://pkg.pr.new/@ngxs/hmr-plugin@2231.tgz ```
``` yarn add https://pkg.pr.new/@ngxs/form-plugin@2231.tgz ```
``` yarn add https://pkg.pr.new/@ngxs/router-plugin@2231.tgz ```
``` yarn add https://pkg.pr.new/@ngxs/storage-plugin@2231.tgz ```
``` yarn add https://pkg.pr.new/@ngxs/store@2231.tgz ```
``` yarn add https://pkg.pr.new/@ngxs/websocket-plugin@2231.tgz ```
commit: b2b3a97
Total files change +1.56KB +1.21%
Final result: :x:
View report in BundleMon website ➡️
No change in files bundle size
Final result: :white_check_mark:
View report in BundleMon website ➡️
Total files change +135B +0.06%
Final result: :white_check_mark:
View report in BundleMon website ➡️
@arturovt I wasn't meaning to remove that test file, but rather to add tests that showcase the cancellation behavior by writing to the state. Potentially the action could write the log entries to the state as well as the recorder.
Then the normal test will show that they are the same, but then when you dispatch an action that results in cancellation, then you will see that the state doesn't receive the writes.
You might want to add an id
to the action so that the triggering action is apparent in the logs.
PS. I view the "don't write to state after unsubscribe" as a different set of tests to the cancellation tests (even though they use the same mechanism).
Code Climate has analyzed commit b2b3a972 and detected 0 issues on this pull request.
The test coverage on the diff in this pull request is 91.6% (50% is the threshold).
This pull request will bring the total coverage in the repository to 95.4% (0.0% change).
View more on Code Climate.
In this commit, we update the implementation of action invocation. The key addition is that we now prevent writing to the state whenever an action handler is unsubscribed (completed or cancelled). Since we have a "unique" state context object for each action being invoked, we can set its
setState
andpatchState
functions to no-ops, essentially making them do nothing when invoked.