Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-10-21 | feat: gn build file format cmd (#155) | H. James Zhao | |
2023-10-20 | feat: add puppet-lint formatter (#153) | Florent Lévigne | |
2023-10-17 | feat: zprint formatter for clojure (#146) | Aron Griffis | |
2023-10-16 | feat: Add config for laravel/pint (#144) | Konstantin Auffinger | |
* 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 | |||
2023-10-15 | feat: add ktlint (#137) | shurizzle | |
2023-10-15 | feat!: merge configs in conform.formatters with defaults (#140) | Steven Arcangeli | |
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. | |||
2023-10-15 | feat: add goimports-reviser (#143) | Aashish KC | |
2023-10-14 | feat: add blue formatter (#142) | frrenzy | |
* Add blue formatter * change description of Blue formatter | |||
2023-10-13 | feat: support for rubyfmt (#139) | Howard Huang | |
Co-authored-by: Github Actions <actions@github> | |||
2023-10-13 | feat: add blade-formatter (#136) | shurizzle | |
2023-10-13 | fix(shellcheck): support filenames with spaces (#135) | pseudometa | |
2023-10-11 | feat: add rufo support (#132) | Estifanos Beyene | |
* feat: add rufo support * feat: shorter description | |||
2023-10-10 | fix: prevent format-after-save autocmd from running on invalid buffers | Steven Arcangeli | |
2023-10-10 | fix: prevent format-on-save autocmd from running on invalid buffers (#128) | Chris Bell | |
2023-10-09 | doc: enforce period at end of formatter description | Steven Arcangeli | |
2023-10-09 | fix: catch and fix more cases of bad-behaving LSP formatters (#119) | Steven Arcangeli | |
2023-10-09 | feat: add fixjson (#126) | Magnus Larsen | |
Co-authored-by: Magnus Larsen <mlar@novozymes.com> | |||
2023-10-08 | ci: use stylua 0.18.2 | Steven Arcangeli | |
2023-10-08 | fix: handle one failure mode with range formatting (#123) | Steven Arcangeli | |
2023-10-08 | feat: errors do not stop formatting early | Steven Arcangeli | |
2023-10-06 | feat: add easy-coding-standard (#121) | Frederik Buchlák | |
* feat: add easy-coding-standard * fix executable | |||
2023-10-06 | fix(biome): do not use stdin due to biome bug (#120) | pseudometa | |
2023-10-05 | feat: expose configuration options for injected formatter (#118) | Steven Arcangeli | |
2023-10-05 | fix: injected formatter handles markdown code blocks in blockquotes (#117) | Steven Arcangeli | |
2023-10-05 | fix: move justfile formatter to correct directory | Steven Arcangeli | |
2023-10-05 | feat: add justfile formatter (#114) | BADR | |
2023-10-05 | doc: typo in runner.lua (#112) | Ikko Eltociear Ashimine | |
ocurred -> occurred | |||
2023-10-04 | fix: support for mix format (#107) | Ethan Gunderson | |
* add support for mix format * split command and set cwd | |||
2023-10-04 | feat: gci formatter for Go (#109) | Kim Nielsen | |
2023-10-03 | fix: phpcbf invalid stdin-path arguments (#108) | Steven Arcangeli | |
2023-10-03 | feat: add phpcbf (#103) | rawalplawit | |
2023-10-02 | fix: format on save autocmds ignore nonstandard buffers | Steven Arcangeli | |
2023-10-02 | fix: injected formatter silent failure on nvim nightly (#100) | Folke Lemaitre | |
2023-10-02 | fix: injected formatter operates on input lines | Steven Arcangeli | |
2023-10-02 | fix: injected formatter doesn't have interruption errors | Steven Arcangeli | |
2023-10-02 | fix: error handling for injected formatter | Steven Arcangeli | |
2023-10-02 | feat: add 'google-java-format' formatter (#99) | Noah Zhu | |
Co-authored-by: Noah Zhu <noah@Noahs-M2-MacBook-Pro-16.local> | |||
2023-10-02 | feat : add astyle formatter (#97) | Rishabh | |
2023-09-30 | feat: add standardrb (#91) | Kerem Bozdas | |
* feat: add standardrb formatter * [docgen] Update docs skip-checks: true --------- Co-authored-by: Github Actions <actions@github> | |||
2023-09-29 | fix: alternations follow notification rules | Steven Arcangeli | |
2023-09-29 | doc: speed up documentation generation | Steven Arcangeli | |
2023-09-29 | feat: metatable to make accessing formatters a bit easier (#89) | Steven Arcangeli | |
2023-09-29 | fix: lsp format calls method from wrong util file | Steven Arcangeli | |
2023-09-29 | fix: injected formatter hangs on empty file | Steven Arcangeli | |
2023-09-29 | fix: injected formatter preserves indentation of code blocks | Steven Arcangeli | |
2023-09-29 | fix: format_after_save blocks on exit for lsp formatting | Steven Arcangeli | |
2023-09-29 | feat: format injected languages (#83) | Steven Arcangeli | |
2023-09-29 | fix: format_after_save autocmd blocks nvim exit until complete | Steven Arcangeli | |
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). | |||
2023-09-29 | fix: only show "no formatters" warning if formatters passed in explicitly (#85) | Steven Arcangeli | |
2023-09-28 | feat: add darker (#80) | okuuva | |
* feat: add darker * fix: darker args Added --no-color since we don't want color output. Also set --revision and --stdin-filename since running darker for a single file doesn't make much sense without them. * refactor: make darker args context aware If the buffer is modified we should set revision and stdin-filename in order not to lose changes. If it's not we should leave them unset so that we respect settings from pyproject.toml. |