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.

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

Optimize the grpc error information: return human readable error information #546

Open
imotai opened this issue Jul 3, 2023 · 0 comments

Comments

@imotai
Copy link
Contributor

imotai commented Jul 3, 2023

Motivations

When the developers got some error information, they don't know what happened.
I hope the human-readable error can solve this problem

  • Would you like to implement this feature? [y/n]
  • Y

Solution

The errors come from the grpc send mutation API
common error

type Errors Readable Level
Invalid Argument the payload or signature is null 1
Invalid Argument the signature is invalid 1
Action Errors Readable Level
Create Document Database 1 Invalid argument: the payload or signature is null
2 Invalid argument: invalid signature with error {}
1
1

Alternatives

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant