feat(mapper): add mapper to proto TangoError#201
Merged
Conversation
justinwon777
force-pushed
the
justin.won/errors
branch
3 times, most recently
from
4149fe6 to
331adab
Compare
justinwon777
force-pushed
the
error-mapper
branch
from
f8c7936 to
f7234f2
Compare
justinwon777
changed the title
sywhang
approved these changes
Jul 16, 2026
No functional changes; goimports reorders tangopb/tango.pb.go's import grouping. gazelle and gofmt reported nothing to change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add a mapper package to convert core/errors.TangoError into the proto TangoError message returned by RPCs.
justinwon777
force-pushed
the
error-mapper
branch
from
f7234f2 to
170c48b
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add mapper to convert core/errors TangoError into the proto TangoError message returned by RPCs.
Stacked on #169
Test Plan
unit test
Issue