Language Server: Herb Linter Fix-on-save#758
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces the functionality for the Herb Language Server to be able to autofix Herb Linter offenses on save.
This builds on the new
--fixoption in the Herb Linter (introduced in #622), which can automatically correct offenses without formatting the rest of the document.If both
Fix-on-SaveandFormat-on-Saveare active, the Language Server will first fix the offenses and then format the document.LSP.Autofix.mp4
The Visual Studio Code Extension also exposes a new "Fix on save" toggle: