Skip to content

Assists which always generate a snippet regardless of snippet capability #17332

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

Open
1 of 3 tasks
DropDemBits opened this issue Jun 2, 2024 · 0 comments
Open
1 of 3 tasks
Labels
A-assists C-bug Category: bug C-tracking-issue Category: tracking issue

Comments

@DropDemBits
Copy link
Contributor

DropDemBits commented Jun 2, 2024

These assists always generate a snippet regardless of if the LSP client does or doesn't support the snippet text edit capability:

They unfortunately weren't captured in the initial batch of migrations to the new structured snippet API as they didn't use {insert,replace}_snippet, which is what I used to figure out which assists needed migrating.

Note that because the structured snippet API (add_{tabstop,placeholder}_*) relies on syntax nodes, they must also be migrated away from using insert and replace.

@DropDemBits DropDemBits added the C-bug Category: bug label Jun 2, 2024
bors added a commit that referenced this issue Jun 3, 2024
…=Veykril

fix: Only generate snippets for `extract_expressions_from_format_string` if snippets are supported

Part of #17332

Fixes `extract_expressions_from_format_string` so that it doesn't generate snippets if the client doesn't support it.
@DropDemBits DropDemBits added the C-tracking-issue Category: tracking issue label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-assists C-bug Category: bug C-tracking-issue Category: tracking issue
Projects
None yet
Development

No branches or pull requests

2 participants