Skip to content

Q LSP: expose actions as "code actions" #802

@justinmk3

Description

@justinmk3

Problem

Q clients commonly provide features like Explain, Optimize, etc., which require very little UI (they send a canned query about code, and return chat responses). But even though the UI is simple, each Q LSP consumer must build this explicitly.

Image

Proposal

Expose code actions for basic features such as Explain, Optimize, etc.

This needs more thought, but at least initially these actions could easily be provided:

  • Explain: sends an "explain this code..." query and shows the response in a 'window/showMessage' event.
  • Optimize: sends an "optimize this code..." query and shows the response in a 'window/showMessage' event.
  • Use window/showMessageRequest to prompt user to select choices from a menu. ref
  • ...others?

This gives an "instant UI" for any LSP client that supports LSP code actions, without any explicit integration with Q LSP.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    tracked[Maintainer-Only] Issue is acknowledged and tracked by the team

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions