fix(scripted_tool): use Display not Debug format in errors#470
Merged
Conversation
…ages
Debug format ({:?}) in error responses could leak internal details
like variant names and struct fields. Switched to Display format
for consistent, user-safe error messages.
Closes #428
chaliy
force-pushed
the
claude/fix-428-Y2nIj
branch
from
56fa487 to
c1153a1
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.
Summary
{:?}(Debug format) which could leak internal detailse.to_string()(Display format) for consistent, safe messagesTest plan
test_error_uses_display_not_debugCloses #428