From b372eec63933e51cc7e08dd87a09b5d93447fcbb Mon Sep 17 00:00:00 2001 From: Juan Cruz Viotti Date: Thu, 24 Sep 2026 17:11:08 -0300 Subject: [PATCH] Remove outdated unsupported YAML documentation comments Signed-off-by: Juan Cruz Viotti --- docs/format.markdown | 2 -- docs/lint.markdown | 11 ++++------- 2 files changed, 4 insertions(+), 9 deletions(-) diff --git a/docs/format.markdown b/docs/format.markdown index 2bdfca049..a18d5703f 100644 --- a/docs/format.markdown +++ b/docs/format.markdown @@ -23,8 +23,6 @@ conventions. Just as code-formatters like `fmt` command to format schemas based on industry-standard conventions and to check their adherence on a continuous integration environment. -**This command does not support YAML schemas yet.** - Examples -------- diff --git a/docs/lint.markdown b/docs/lint.markdown index fa7edc980..139507097 100644 --- a/docs/lint.markdown +++ b/docs/lint.markdown @@ -39,13 +39,10 @@ automatically fix many of them. > rest of the description. If you are working with JSON Schema for API > specifications, you should make use of both linters together! -**The `--fix/-f` option is not supported when passing YAML schemas.** - -**The `--format/-m` option requires `--fix/-f` to be set and is not supported -for YAML schemas.** When `--format/-m` is set, the output file is always -written with proper formatting (equivalent to running `fmt`), even if there -are no lint issues to fix. Use `--keep-ordering/-k` with `--format/-m` to -preserve key ordering during formatting. +When `--format/-m` is set, the output file is always written with proper +formatting (equivalent to running `fmt`), even if there are no lint issues to +fix. Use `--keep-ordering/-k` with `--format/-m` to preserve key ordering +during formatting. > [!NOTE] > There are linting rules that require compiling and validating instance