Closed cevr closed 5 months ago
Latest commit: 8ec3f9ac5a2e63ab9b76c3d3a6b3e2d23b730766
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
@Andarist Thanks for the quick review! I added some more test cases in line with your comments, and opted to using a WeakMap to capture references to unique actors, since id
is not guaranteed to be unique within a machine.
What are your thoughts on that?
Using WeakMap
is fine 👍
@Andarist Updated the tests. Though I had to add ESNext.Promise
to the tsconfig lib
. Is that alright?
also my changes in 29ae633
(#4832) seem to have broken one seemingly unrelated test 🤔 not sure how yet
also my changes in 29ae633 (#4832) seem to have broken one seemingly unrelated test 🤔 not sure how yet
it's a common~ issue with async tests that share a thread ;p an error that was "created" by one of the tests might get thrown (and caught by the global handler) while another test is already executing
Currently there is no notion of cancelling promises that are passed into a
fromPromise
logic creator if the state transitions before the promise is resolved.This is a problem if the promise has side effects that run after resolving/rejecting - eg retries, cache invalidations, etc.
Now the signal can be used to cancel any side effects