📝 document error boundaries and the scoped() function
#960
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
taras
approved these changes
Jan 8, 2025
Comment on lines
+16
to
+21
| * function* example() { | ||
| * let signal = yield* scoped(function*() { | ||
| * return yield* useAbortSignal(); | ||
| * }); | ||
| * return signal.aborted; //=> true | ||
| * } |
There was a problem hiding this comment.
This is a beautiful little piece of code 😍
The way error boundaries are created has changed from `v3` to `v4`. Instead of using `call()` or `action()` to establish an error boundary, there is now a dedicated `scoped()` function which not only traps any errors, but also creates a resource boundary that does not let any resource or task escape. This updates the error documentation, and also adds documentation to the `scoped()` function. Finally, there was an old deno link that I updated to JSR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
The way error boundaries are created has changed from
v3tov4. Instead of usingcall()oraction()to establish an error boundary, there is now a dedicatedscoped()function which not only traps any errors, but also creates a resource boundary that does not let any resource or task escape.Approach
This updates the error documentation, and also adds documentation to the
scoped()function. Finally, there was an old deno link that I updated to JSR.