| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* feat: add new format option: undojoin
This option allow user to automatically perform undojoin command before
formatting. This is useful if the user uses an autosave plugin + format
on save, because in case of undo, it will undo the last change AND the
formatting. Without this option, it will only undo the formatting.
* fix: passed linting
* fix: apply undojoin for LSP formatting
* doc: fix type annotations for apply_format
* doc: regenerate documentation
---------
Co-authored-by: Steven Arcangeli <stevearc@stevearc.com>
|
|
* feat(shfmt): automatically detect indentation
* fix(markdown-toc): improve correctness of indentation size calculation
* fix(djlint): improve correctness of indentation size calculation
* feat: add effective `shiftwidth` to `conform.Context`
this also refactors formatters that automatically set indentation level
to use the new shiftwidth context
|
|
|
|
the extension used to be always the file type, be smarter now. For
instance prettier wouldn't recognize a `.typescript` extension.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
formatters (#273)
* feat: add dry_run option and pass return values for if buffer would be modified
* fix: implement dry_run for blocking calls to lsp formatter
* refactor: change `changed` variable to `did_edit`
* docs: Update README
* fix: address PR comments
* fix: small cleanups
---------
Co-authored-by: Steven Arcangeli <stevearc@stevearc.com>
|
|
* Fix(black): formatting excluded files results in blank buffer (#249)
* Fixed stylua formatting
* Fixed more stylua formatting
* Log buffer name and change from trace to warning
* Test fix: set_formatter_output funtion was moved out of test_util
* Avoid blank output triggering errors in fuzzer tests
|
|
|
|
|
|
This is a breaking API change, but there is a shim in place that will keep existing functions working, just with a warning notification. Most people should not encounter this at all. For anyone overriding a formatter config value with a function that takes `(ctx)` as the parameter, it will need to be updated to take `(self, ctx)`.
|
|
|
|
|
|
|
|
|
|
|
|
ocurred -> occurred
|
|
|
|
|
|
|
|
|
|
This fixes one the main issue with a BufWritePost format autocmd:
that if the user does `:wq` vim will exit before the formatting changes
are applied. Now we will block in VimLeavePre until the formatter
completes (or a timeout is reached).
|
|
|
|
|
|
|
|
* refactor: replicate lsp.buf.format call
* feat: format() takes an optional callback
* fix: improper logging
* fix: callback returns error if buffer is no longer valid
* fix: provide more detailed error message to callback
* fix: properly detect task interruption
* cleanup: remove unnecessary error code translation
* fix: lsp formatting for Neovim 0.9
* doc: add example of async formatting on save
* fix: async LSP formatter discards changes if buffer was modified
* fix: error code comparison
* fix: use the same LSP client filtering logic everywhere
* fix: add buffer validity guard checks
* fix: add buffer validity guard to LSP formatter
* refactor: change the default log level to WARN
|
|
* feat: apply changes as text edits using LSP utils
This means we can leverage all of the work that was done in the LSP
client to preserve marks, cursor position, etc
* log: add trace logging to debug performance
* feat: use the same diff -> TextEdit technique for bad LSP servers
Some LSP servers simply return a single TextEdit that replaces the whole
buffer. This is bad for extmarks, cursor, and if the buffer is open in
multiple windows the non-active window will jump to the top. We can
detect that situation and apply the same vim.diff logic to convert it
into more granular TextEdits.
|
|
|
|
|
|
|
|
|
|
Should work the same as vim.lsp.buf.format(). Additionally, range
formatting is supported for *any* formatter. If the formatter doesn't
have native support for ranges, conform will do its best to only apply the
diffs that affect that range.
|
|
|
|
|
|
Since we're applying diffs instead of replacing the entire buffer, the
cursor actually stays in a more predictable location if we _don't_ try
to save & restore the window views.
|
|
|
|
|
|
|
|
|
|
|
