fix: Add newline after directory depth message in fs_read tool output #1978
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
|
Someone got to it before me, this has been on my todo list for a while. |
|
resolved |
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.
Description
This PR adds a missing newline character after the directory depth message in the fs_read tool's output formatting. The change improves readability by ensuring proper line breaks between the depth information and subsequent directory content listings.
Changes
queue_descriptionmethod in theFsDirectorystruct to include a newline character at the end of the depth message outputBefore:
Reading directory: /amazon-q-developer-cli/crates/cli/src/cli/chat/tools with maximum depth of 0Reading: crates/cli/src/cli/chat/tools
After:
Reading directory: /amazon-q-developer-cli/crates/cli/src/cli/chat/tools with maximum depth of 0
Reading: crates/cli/src/cli/chat/tools
Testing
Verified that the output now correctly displays with proper line breaks when using the fs_read tool in directory mode with depth parameter.
Related Issues
N/A