-
Notifications
You must be signed in to change notification settings - Fork 22
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
Editorial: Change exceptions to be more precise #70
Conversation
This seems to include some of the other changes. Should we work on those first and then rebase this? |
Whoops, sorry about that. I hadn't meant to include those other changes here. There's some merge conflicts so I'll rebase once the other changes merge |
It seems this has been impacted by whatwg/whatwg.org#401. Will try to sort that, but not sure about the timeline. |
By the way, you want stuff like "Fixes #63" to be in the commit message body so you don't have to visit the PR to find the issue discussion. |
Before: `throw a {{SecurityError}}` After: `[=throw=] a "{{SecurityError}}" {{DOMException}}` See whatwg/fs#63 and whatwg/fs#89. Fixed in the upstream spec in whatwg/fs#70 and whatwg/fs#91, respectively
Before: `throw a {{SecurityError}}` After: `[=throw=] a "{{SecurityError}}" {{DOMException}}` See whatwg/fs#63 and whatwg/fs#89. Fixed in the upstream spec in whatwg/fs#70 and whatwg/fs#91, respectively SHA: a350a87 Reason: push, by @a-sully Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Fixes #63
Before: {{InvalidStateError Error}}
After: "{{InvalidStateError Error}}" {{DOMException}}
Preview | Diff