Closed OnlyWick closed 8 months ago
Latest commit: b406a0b3cd0ed17a1425989bb20d6c46c6fd96ae
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Name | Link |
---|---|
Latest commit | b406a0b3cd0ed17a1425989bb20d6c46c6fd96ae |
Latest deploy log | https://app.netlify.com/sites/preact-signals-demo/deploys/65e84f149d78e80008b729bd |
Deploy Preview | https://deploy-preview-516--preact-signals-demo.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
I don't think we can remove this try/catch: without it, a custom ._notify
implementation throwing would cause the graph to become incorrect, which would break all signals+computeds in very unexpected ways.
Will it happen when used together with other frameworks? I see in the core
that _notify
does not throw any errors.
there are no operations in the
notify
method that could cause program interruption.