-
Notifications
You must be signed in to change notification settings - Fork 665
fix(go): preserve error chain in GenkitError via Unwrap #4527
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
Open
Zereker
wants to merge
4
commits into
firebase:main
Choose a base branch
from
Zereker:fix/go-genkit-error-unwrap
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
668b317
fix(go): implement Unwrap for GenkitError to support error chains
DEVMANISHOFFL 0b76ae6
fix: remove accidental telemetry changes and optimize error scan
DEVMANISHOFFL 110e9c3
test(go): add comprehensive error chain subtests for GenkitError
Zereker 7151e05
refactor(go/core): omit empty details in ToReflectionError JSON output
Zereker File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The defensive
nilcheck fore.Detailsis a good addition to prevent panics. However, the current implementation always allocateserrDetails, which results in adetails: {}field in the JSON output even when no stack or trace ID is present. This behavior doesn't leverage theomitemptytag on theDetailsfield in theReflectionErrorstruct.To produce a cleaner JSON output and align with the
omitemptyintention, we can refactor this to allocateerrDetailsonly when there are actual details to include. This will cause thedetailsfield to be omitted from the JSON when it's empty.