-
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
Handle errors from JSON serialization. #666
Conversation
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.
LGTM
SHA: 026dbaa Reason: push, by cbiesinger Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@@ -1208,6 +1208,7 @@ To <dfn>fetch an identity assertion</dfn> given a {{USVString}} | |||
1. If |provider|'s {{IdentityProviderRequestOptions/params}} is not empty: | |||
1. Let |json| be the result of [=serializing a JavaScript value to a JSON string=] | |||
with |provider|'s {{IdentityProviderRequestOptions/params}}. | |||
1. If serializing threw an exception, return failure. |
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.
should this be "through" instead of "threw"?
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.
should this be "through" instead of "threw"?
Nope. "Threw" is a past tense of "throw".
SHA: 026dbaa Reason: push, by pull[bot] Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Preview | Diff