Age | Commit message (Collapse) | Author |
|
skip-checks: true
|
|
`biome` formatter uses `biome format` command which applies formatting but doesn't apply lint autofixes.
Couldn't find a better way then to create another formatter that uses `biome check", --apply-unsafe`
|
|
skip-checks: true
|
|
|
|
`swift-format` won't pick up `.swift-format` config file in stdin mode. We need to set `stdin = false` and `--in-place` to make it work with `conform.nvim`.
[apple/swift-format/README.md](https://github.com/apple/swift-format/blob/e312ede68bd8549381f9e2edfef7e6c176e9a50e/README.md#L129-L131)
> * `-i/--in-place`: Overwrites the input files when formatting instead of
printing the results to standard output. _No backup of the original file is
made before it is overwritten._
Fix https://github.com/stevearc/conform.nvim/issues/211
|
|
|
|
skip-checks: true
|
|
|
|
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
|
|
|
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
|
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>
|
|
|
|
|
|
file (#272)
solves: https://github.com/stevearc/conform.nvim/issues/271
|
|
|
|
|
|
|
|
|
|
skip-checks: true
|
|
|
|
|
|
|
|
* 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
|
|
skip-checks: true
|
|
* feat: add xmllint formatter
* doc: shorten xmllint description
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
|
|
|
|
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
skip-checks: true
|
|
|
|
This ensures a much quicker execution on 2nd and any subsequent run. Otherwise there's always a 1-3 seconds delay before formatting is being applied (as rubocop is not that quick).
From rubocop's documentation:
```
--server If a server process has not been started yet, start the server process and execute inspection with server.
```
|
|
|
|
|
|
filetype and extension (#241)
|
|
This makes the behavior of formatexpr more consistent with
`vim.lsp.formatexpr`; do not run vim's builtin formatter.
Problem: When conform's formatexpr is used and (range or buffer) but
conform can't do formatting and there is no LSP formatter with the
formatting capabilities, it will fall back to the (wrong) built-in
formatting, which might result in simply concatenating all the words.
This is a breaking change, reverting the behavior introduced in #55.
|
|
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
|
skip-checks: true
|
|
|
|
skip-checks: true
|
|
|
|
|
|
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)`.
|
|
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
|
* fix: load temp buffer once created to load the context for formatters
* fix: use `_injection_query` to decide if the `injection` formatter is valid
|