-
Notifications
You must be signed in to change notification settings - Fork 37
Error responses for DC API #556
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
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.
added proposal for example and realized @c2bo was quicker ;-)
|
WG discussion:
|
tplooker
left a comment
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.
Approved, on the basis that @c2bo suggested change is accepted.
Co-authored-by: Christian Bormann <8774236+c2bo@users.noreply.github.com>
GarethCOliver
left a comment
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.
Added the privacy consideration section (please read/review)
Co-authored-by: Tobias Looker <tplooker@gmail.com>
Co-authored-by: Tim Cappalli <tim@cappalli.me>
Co-authored-by: Tim Cappalli <tim@cappalli.me>
Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com>
|
WG discussion:
|
Co-authored-by: Christian Bormann <8774236+c2bo@users.noreply.github.com>
|
issue will be opened to follow up on the error code. |
Co-authored-by: Martijn Haring <62745275+martijnharing@users.noreply.github.com>
Closes #204
Probably needs some word smithing but adds some text Appendix A around the format of the error response and a note that protocol errors will still result in a fulfilled promise at the DC API layer.
@GarethCOliver feel free to just push to this same branch / PR with the privacy considerations.