Age | Commit message (Collapse) | Author |
|
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.
|
|
|
|
|
|
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)`.
|
|
* fix: load temp buffer once created to load the context for formatters
* fix: use `_injection_query` to decide if the `injection` formatter is valid
|
|
* feat: add jsonnetfmt
* fix: use stdin
* docs: adjust name
* docs: adjust url
|
|
* chore: remove $FILENAME from standardjs config
* fix(biome): use first local executable over global
|
|
|
|
|
|
|
|
With the release of v1.4.0, biome now supports the arguments needed for formatting via stdin/stdout. If you are using an older version of biome, you can override the formatter configuration to use the previous settings.
|
|
|
|
|
|
|
|
|
|
* feat: add beancount formatter
* lint: remove unused require
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* feat: add cbfmt
* lint: fix style
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
* feat: add phpinsights
* doc: remove redundant mention of formatting in description
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
* feat: add `auto-optional`
* doc: add period at end of description
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
|
|
* feat: add styler formatter for R
* fix: do not run --vanilla to pick up options
* docs: add to README
* fix: std in false
* fix: do not hardcode style, use config file
* fix: lint styler formatter
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* feat: add mdslw markdown formatter
* lint: remove unused import
---------
Co-authored-by: Torsten Long <torsten.s.long@gmail.com>
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
cli2 is a better cli for markdownlint. It allows to have config files in different directories, and it's also from the same author as the original node.js markdownlint lib.
|
|
* feat: add usort
* formatting via stdin
|
|
* Add formatter and update readme and conform.txt
* Remove unused variable
|
|
* feat: add tlint
* update doc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* feat: Add config for laravel/pint
- Supports both mason and local composer install
* chore: Add pint to formatters list in readme
* Revert "chore: Add pint to formatters list in readme"
This reverts commit 8edb456a086642076931b4dd8666b02e5311e1e0.
* fix: remove unnecessary mason executable path
* fix: Change meta description to it's short form
|
|
|
|
This breaking change should make it significantly easier to modify formatters. While I expect 99% of configs to be backwards-compatible, this can still potentially cause problems. If you:
* define a formatter in the `formatters` option
* that has the same name as a built-in formatter
* and omits a property from the original formatter (e.g. leaves out `range_args` or `cwd`)
Then you may encounter breaking behavior from this commit, because now your config definition will be merged with the built-in definition, and so will inherit those omitted properties. This config merging behavior can be opted-out of by adding `inherit = false` to your formatter config.
|