feat: apply source.organizeImports and source.fixAll during lsp format#75
Merged
Conversation
Owner
|
Looks good though. The test looks broken (not because of this MR). |
Owner
|
I fixed the CI, please format with |
Contributor
Author
|
Thanks for the tip about stylua! The format should be fixed now. |
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
2 participants
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.
Using
lspfor formatting wasn't tidying up imports.This change adds the two additional formatting features to the
lspformatter:source.organizeImports- goimports functionalitysource.fixAll- very conservative code fixesFor details see the
goplsdocs here.vim.lsp.buf.code_action()is currently asynchronous only so theapply_code_actions_sync()uses a small hack to get the code actions applied synchronously.