refactor: change error definition in auth PKG to Bucketeer error #2133
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # pkg/error/error.go
# Conflicts: # pkg/error/error.go
# Conflicts: # pkg/auth/api/api.go # pkg/auth/google/authenticator.go
# Conflicts: # pkg/error/error.go
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request refactors error handling in the authentication service to use a more consistent and structured approach. Instead of manually constructing gRPC status errors with localized messages, the code now utilizes the
api.NewGRPCStatushelper and centralizes error definitions using the new error package. This improves maintainability and standardizes error responses across the authentication API.I have also standardized the process of assigning ErrorInfo to GRPCStatus for each error via
api.NewGRPCStatus.This ErrorInfo will be used when moving i18n to the frontend(#1253), and we plan to generate error messages etc. based on this information on the frontend.