Skip to content

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

Description

@imotai

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions