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

@ command parsing conflicts with chatting about literal Java annotations, Python decorators, C# verbatim strings, etc. #89

Closed
2 of 4 tasks
senorflor opened this issue Aug 7, 2024 · 0 comments · Fixed by #95
Labels
bug Something isn't working

Comments

@senorflor
Copy link

senorflor commented Aug 7, 2024

Problem

Steps to reproduce the issue

  1. Type any code that includes a @ symbol, e.g. @SomeAnnotation in Java @Decorator in Python, @instance_var in Ruby, etc.
  2. Observe special syntax highlighting from @ character onwards, e.g.
  3. Type enough characters so that word is not in the command picker, then Spacebar or Tab
  4. Token starting at @ is deleted

Expected behavior

  1. Either:
  • Once the identifier was no longer in the command list, I would expect the token to lose syntax highlighting and to be left intact, allowing entry of such code elements into chat with the underlying service/model.
  • Alternately, I would expect some combination of escape characters, e.g. `@backtick_fencing` or \ prefixing, to allow the entry of @IdentifiersLikeThis without command parsing.

System details

  • OS: MacOS 14.5
  • Tested environment:
    • Web (Demo app)
    • VSCode Amazon Q Chat
    • JetBrains IntelliJ Amazon Q Chat
  • Enviroment extension version (if applicable):
  • Enviroment is remote
@senorflor senorflor added the bug Something isn't working label Aug 7, 2024
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.

1 participant