Refactor errors to expose a kind & meta field separately #249
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: Fixes #110 Fixes #111
Description of changes: This diff improves our errors by introducing a
kind
field that captures the variant separately frommeta
which captures metadata about the error (eg. request id).This is on the path to adding a top-level error for the entire service. Operations will return the errors as they do now, but they will all be convertible into the top level error. This is to facilitate generic error handling across operations.
I also simplified and optimized the implementation of
retryable_error_kind
, cutting out about 1k lines of generated codeBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Generated code diff for context: main-generated...error-kind-generated