aboutsummaryrefslogtreecommitdiffstats
path: root/doc/recipes.md
AgeCommit message (Collapse)Author
2024-07-19doc: recipe for running first available formatter and then othersSteven Arcangeli
2024-07-19doc: add recipe for leaving visual mode after formatSteven Arcangeli
2024-07-19refactor: deprecate formatter alternation syntaxSteven Arcangeli
2024-07-19feat: allow configuring conform.format() args on a per-filetype basisSteven Arcangeli
2024-06-17feat!: expand options for LSP formatting (#456)Steven Arcangeli
2023-10-15feat!: 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-02doc: add a recipe for complete lazy.nvim configurationSteven Arcangeli
2023-09-29feat: format injected languages (#83)Steven Arcangeli
2023-09-26feat: another utility for extending formatter argumentsSteven Arcangeli
2023-09-16fix: unify timeout error message format with LSPSteven Arcangeli
2023-09-15feat: utility function to extend the built-in formatter args (#50)Steven Arcangeli
2023-09-15[docgen] Update docsGithub Actions
skip-checks: true
2023-09-15doc: recipe for automatically running slow formatters asyncSteven Arcangeli
2023-09-14doc: add some recipes to the documentationSteven Arcangeli