-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Error Standardization: Cryptography API #7491
Labels
good first issue
Good for newcomers
Comments
/assign |
This was referenced Feb 19, 2024
/assign |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Richer errors in Dapr for the Cryptography API.
Note: Please clone this issue and assign the clone of this issue to yourself if you would like to contribute to the error standardization efforts.
Scope of work
Definition of done
Keep in mind
Unless a major version is being released and there is a solid reason for introducing backwards incompatibility, we can't change the API, meaning the HTTP and gRPC status codes, and the error codes must stay the same. An exception to this is the gRPC
StatusCode.UNKNOWN
which should be converted to a specific status.See the kit errors pkg README for another usage example. For each error being updated, you can use the following helper functions to add error details, see the kit errors pkg for more details:
WithHelpLink()
WithHelp()
WithErrorInfo()
- RequiredWithFieldViolation()
WithDetails()
Reference PRs
Existing error standardization for:
The text was updated successfully, but these errors were encountered: