Skip to content

fix: ux polishing for read tool messages. #1070

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
merged 1 commit into from
Apr 22, 2025
Merged

Conversation

laileni-aws
Copy link
Contributor

@laileni-aws laileni-aws commented Apr 22, 2025

Problem

  • Existing plugin shows read files multiple times and emitted per file.

image

Solution

image

TODO:

  • I will send out a follow up PR supporting List directory UX changes and mode refactored code.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@laileni-aws laileni-aws marked this pull request as ready for review April 22, 2025 21:33
@laileni-aws laileni-aws requested a review from a team as a code owner April 22, 2025 21:33
Comment on lines +44 to +46
getMessageIdToUpdate(): string | undefined {
return this.#state.messageIdToUpdate
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: if we add more message types, is this actually the 'read/query/search' message to update, and there might be others in the future?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I agree
I am trying to use this same messageIdToUpdate for all the messages from read, list and grep(future). So we will be having only one messageId and can update all the messages contextList using this messageId.
Thats the plan if there are no challenges!

@laileni-aws laileni-aws merged commit e83d7ba into aws:main Apr 22, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants