Skip to content

Don't tie force_autofix to client capabilities #2420

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
Jul 22, 2025

Conversation

Techatrix
Copy link
Member

The force_autofix config option would previously be ignored if the client capabilities indicated support for code actions. The intent was to prevent this config option from being enabled in editors that could natively run code action on save. However, there is no reliable way to detect whether a client supports code actions on save so this prevented autofix from being accessible in some editors (Helix).

The `force_autofix` config option would previously be ignored if the
client capabilities indicated support for code actions. The intent was
to prevent this config option from being enabled in editors that could
natively run code action on save. However, there is no reliable way to
detect whether a client supports code actions on save so this prevented
autofix from being accessible in some editors (Helix).
@Techatrix Techatrix force-pushed the techatrix/force-autofix branch from 7d48ccf to 8ae4f82 Compare July 22, 2025 18:26
@Techatrix Techatrix merged commit 4b56f74 into master Jul 22, 2025
6 checks passed
@Techatrix Techatrix deleted the techatrix/force-autofix branch July 22, 2025 18:29
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.

1 participant