Skip to content
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

Up/down prompt history navigation causes extra ``` in code attachments #199

Closed
3 of 4 tasks
Jurredr opened this issue Dec 9, 2024 · 0 comments · Fixed by #200 or #201
Closed
3 of 4 tasks

Up/down prompt history navigation causes extra ``` in code attachments #199

Jurredr opened this issue Dec 9, 2024 · 0 comments · Fixed by #200 or #201
Assignees
Labels
bug Something isn't working

Comments

@Jurredr
Copy link
Contributor

Jurredr commented Dec 9, 2024

Problem

When going to a previous prompt in history using the up or down arrows, code attachments suddenly have ``` attached to both the start and the end of the code block.

image
image

Steps to reproduce the issue

Send a message with code attachment, then go to that message in history by pressing the up arrow in the prompt input.

Expected behavior

The code attachment block should look the same as when initially attached (so without ``` visible at the start and end).

System details

Behaviour is visible in both VSCode and JetBrains. However, on the web example app it does not seem to happen.

  • OS:
  • Tested enviroment:
    • Web (Demo app)
    • VSCode Amazon Q Chat
    • JetBrains IntelliJ Amazon Q Chat
  • Enviroment extension version (if applicable):
  • Enviroment is remote
@Jurredr Jurredr added the bug Something isn't working label Dec 9, 2024
@Jurredr Jurredr linked a pull request Dec 9, 2024 that will close this issue
2 tasks
@francescoopiccoli francescoopiccoli linked a pull request Dec 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants