Intent to Ship: Error.cause property

[Victor Gomes]

Contact emails

victo...@chromium.org

Explainer

None

Specification

https://github.com/tc39/proposal-error-cause

Summary

Adds an additional options parameter to the Error() constructor with a cause property, the value of which will be assigned to the error instances as a property. This allows errors to be chained without unnecessary and overelaborate formalities on wrapping the errors in conditions.

Blink component

Blink>JavaScript>Language

Search tags

JavaScript, Error

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

None

Gecko: TC39 Stage 3 feature

WebKit: TC39 Stage 3 feature

Web developers: TC39 Stage 3 feature

Is this feature fully tested by web-platform-tests?

No

Tested by test262:
https://github.com/tc39/test262/blob/main/test/built-ins/Error/cause_property.js
https://github.com/tc39/test262/blob/main/test/built-ins/Error/cause_abrupt.js

Flag name

--harmony-error-cause

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1192162

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5727099325251584

This intent message was generated by Chrome Platform Status.

[Daniel Bratell]

LGTM1

/Daniel

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGFuzY1AorjfOfbAoF7f-8%3DSs3gpQZZH2E8OuQNKhjne9Uyr0g%40mail.gmail.com.

[Chris Harrelson]

LGTM2, but please ping Webkit and Mozilla via bit.ly/blink-signals to inform them, encourage coordinated launch, and gather any late-breaking concerns.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7749da46-bf2f-9e09-e37b-c5593af1dc53%40gmail.com.

[Chris Harrelson]

I take back my signals comment. I discussed with the other API owners, and we concluded you don't need to ask for signals in this case, since it's a stage 3 proposal.

[Daniel Bratell]

Btw, what has Firefox people said about the collision in the Error constructor?

/Daniel

[Rick Byers]

LGTM3

I'm very glad to see this pattern coming to JS. I always thought this model worked quite well in practice in my previous life working with .NET.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e645f68a-7a0e-78ef-3c79-7773715442c0%40gmail.com.

[Yulia Startsev]

Daniel,

You asked about the collision in the error constructor on Firefox: We checked this pretty early on and it isn't an issue. The proposal uses an options bag as opposed to a number, and we just type check for that. We have an in progress implementation that should land soon.

Yulia

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9QE883vd0H_nHGGR0m5G4-1sCp24W8HhXpviHhR8%3DQUw%40mail.gmail.com.

[Daniel Bratell]

Good that it doesn't cause any implementation problems!

/Daniel