Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
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)`.
|
|
skip-checks: true
|
|
skip-checks: true
|
|
skip-checks: true
|
|
skip-checks: true
|
|
|
|
skip-checks: true
|
|
skip-checks: true
|
|
* feat: add beancount formatter
* lint: remove unused require
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
skip-checks: true
|
|
skip-checks: true
|
|
skip-checks: true
|
|
* feat: add cbfmt
* lint: fix style
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
skip-checks: true
|
|
* feat: add phpinsights
* doc: remove redundant mention of formatting in description
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
skip-checks: true
|
|
* feat: add `auto-optional`
* doc: add period at end of description
---------
Co-authored-by: Steven Arcangeli <506791+stevearc@users.noreply.github.com>
|
|
skip-checks: true
|
|
* 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
|
|
skip-checks: true
|
|
|
|
|
|
skip-checks: true
|
|
skip-checks: true
|
|
|
|
skip-checks: true
|
|
skip-checks: true
|
|
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
|
|
skip-checks: true
|
|
* Add formatter and update readme and conform.txt
* Remove unused variable
|
|
* feat: add tlint
* update doc
|
|
|
|
skip-checks: true
|
|
skip-checks: true
|
|
skip-checks: true
|
|
|
|
skip-checks: true
|
|
skip-checks: true
|
|
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.
|
|
skip-checks: true
|
|
skip-checks: true
|
|
skip-checks: true
|
|
skip-checks: true
|
|
skip-checks: true
|
|
* feat: add rufo support
* feat: shorter description
|