-
Notifications
You must be signed in to change notification settings - Fork 72
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
feat(ses,pass-style,marshal): permit Promise.any, AggregateError, cause #2042
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
User-visible changes in `@endo/common`: | ||
|
||
# Next release | ||
|
||
- `throwLabeled` parameterized error construction | ||
- Like the assertion functions/methods that were parameterized by an error | ||
constructor (`makeError`, `assert`, `assert.fail`, `assert.equal`), | ||
`throwLabeled` now also accepts named options `cause` and `errors` in its | ||
immediately succeeding `options` argument. | ||
- Like those assertion functions, the error constructor argument to | ||
`throwLabeled` can now be an `AggregateError`. | ||
If `throwLabeled` makes an error instance, it encapsulates the | ||
non-uniformity of the `AggregateError` construction arguments, allowing | ||
all the error constructors to be used polymorphically | ||
(generic / interchangeable). | ||
- The error constructor argument is now typed `GenericErrorConstructor`, | ||
effectively the common supertype of `ErrorConstructor` and | ||
`AggregateErrorConstructor`. |
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
User-visible changes in `@endo/errors`: | ||
|
||
# Next release | ||
|
||
- `AggegateError` support | ||
- Assertion functions/methods that were parameterized by an error constructor | ||
(`makeError`, `assert`, `assert.fail`, `assert.equal`) now also accept named | ||
options `cause` and `errors` in their immediately succeeding | ||
`options` argument. | ||
- For all those, the error constructor can now be an `AggregateError`. | ||
If they do make an error instance, they encapsulate the | ||
non-uniformity of the `AggregateError` construction arguments, allowing | ||
all the error constructors to be used polymorphically | ||
(generic / interchangeable). | ||
- Adds a `GenericErrorConstructor` type to be effectively the common supertype | ||
of `ErrorConstructor` and `AggregateErrorConstructor`, for typing these | ||
error constructor parameters that handle the error constructor | ||
polymorphically. | ||
- The SES `console` now includes `error.cause` and `error.errors` in | ||
its diagnostic output for errors. |
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
This seems too disruptive; we should only skip the narrow subset of test logic that won't work as expected.