Skip to content
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.

Sign up for GitHub

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

Jump to bottom

support for any error details #2389

Closed
akornatskyy opened this issue Mar 9, 2023 · 1 comment
Closed

support for any error details #2389

akornatskyy opened this issue Mar 9, 2023 · 1 comment

Comments

@akornatskyy
Copy link

According to status.proto, details is of type Any. The current implementation accepts only string for error details and communicates via http2 header.

The details could be a result of field validation, meaning it could be a list of objects or similar.

What would be a better way to communicate error details besides: (a) JSON.stringify() to details, (b) some custom metadata string key, which implies JSON.stringify(), (c) a binary metadata key, which implies base64 encoding?
@murgatroid99
Copy link
Member

Please see previous discussions in #184, #1613, and #2120.

@murgatroid99 murgatroid99 closed this as not planned Won't fix, can't repro, duplicate, stale Mar 9, 2023
@murgatroid99 murgatroid99 mentioned this issue Apr 3, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@murgatroid99 @akornatskyy