-
Notifications
You must be signed in to change notification settings - Fork 1
refactor: reduce complexity of execute_safe_output in src/execute.rs
#307
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
Merged
jamesadevine
merged 4 commits into
main
from
refactor/reduce-execute-safe-output-complexity-e770d6360ee7e02e
Apr 23, 2026
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
d922b96
refactor: reduce complexity of execute_safe_output in src/execute.rs
github-actions[bot] c110347
refactor: use macro table for execute tool dispatch
Copilot 6f8c02f
refactor: simplify macro error flow in execute dispatch
Copilot 02e0e09
fix: restore field-level executor debug logs
Copilot 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
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.
@copilot Anyway we could clean this up further with a macro approach instead? Is there something clever we could do with serde to deserialize the SafeOutputs by name automatically?
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.
Implemented a macro-backed dispatch table in
execute_safe_outputto reduce the remaining repetitive tool-name/type mapping (6f8c02f). I also adjusted it to returnResult<Option<_>>instead of using?inside the macro body for clearer error flow. For serde auto-deserialization byname, we could model a tagged enum, but that would require broader per-tool type reshaping; this keeps the change minimal and localized.No UI changes in this PR, so there isn’t a UI screenshot to share.