diff --git a/crates/biome_cli/tests/snapshots/main_commands_check/check_help.snap b/crates/biome_cli/tests/snapshots/main_commands_check/check_help.snap index d484b7bfa42f..b9ff147c5970 100644 --- a/crates/biome_cli/tests/snapshots/main_commands_check/check_help.snap +++ b/crates/biome_cli/tests/snapshots/main_commands_check/check_help.snap @@ -87,10 +87,11 @@ Available options: --formatter-enabled= Allow to enable or disable the formatter check. --linter-enabled= Allow to enable or disable the linter check. --organize-imports-enabled= Allow to enable or disable the organize imports. - --stdin-file-path=PATH A file name with its extension to pass when reading from standard in, - e.g. echo 'let a;' | biome check --stdin-file-path=file.js" + --stdin-file-path=PATH Use this option when you want to format code piped from `stdin`, and + print the output to `stdout`. The file doesn't need to exist on disk, what matters is the extension of - the file. Based on the extension, Biome will use the appropriate tool. + the file. Based on the extension, Biome knows how to check the code. + Example: `echo 'let a;' | biome check --stdin-file-path=file.js` -h, --help Prints help information ``` diff --git a/crates/biome_cli/tests/snapshots/main_commands_format/format_help.snap b/crates/biome_cli/tests/snapshots/main_commands_format/format_help.snap index 0b7ec727956e..169fe755d0d2 100644 --- a/crates/biome_cli/tests/snapshots/main_commands_format/format_help.snap +++ b/crates/biome_cli/tests/snapshots/main_commands_format/format_help.snap @@ -88,10 +88,11 @@ Available options: languages) files. Default to 2. --json-formatter-line-width=NUMBER What's the max width of a line, applied to JSON (and its super languages) files. Defaults to 80. - --stdin-file-path=PATH A file name with its extension to pass when reading from standard in, - e.g. echo 'let a;' | biome format --stdin-file-path=file.js". + --stdin-file-path=PATH Use this option when you want to format code piped from `stdin`, and + print the output to `stdout`. The file doesn't need to exist on disk, what matters is the extension of - the file. Based on the extension, Biome will use the appropriate tool. + the file. Based on the extension, Biome knows how to format the code. + Example: `echo 'let a;' | biome format --stdin-file-path=file.js` --write Writes formatted files to file system. -h, --help Prints help information diff --git a/crates/biome_cli/tests/snapshots/main_commands_lint/lint_help.snap b/crates/biome_cli/tests/snapshots/main_commands_lint/lint_help.snap index 2e4b14351cfe..f6dc40d8e648 100644 --- a/crates/biome_cli/tests/snapshots/main_commands_lint/lint_help.snap +++ b/crates/biome_cli/tests/snapshots/main_commands_lint/lint_help.snap @@ -53,10 +53,11 @@ Available positional items: Available options: --apply Apply safe fixes, formatting --apply-unsafe Apply safe fixes and unsafe fixes, formatting and import sorting - --stdin-file-path=PATH A file name with its extension to pass when reading from standard in, - e.g. echo 'let a;' | biome lint --stdin-file-path=file.js" + --stdin-file-path=PATH Use this option when you want to format code piped from `stdin`, and + print the output to `stdout`. The file doesn't need to exist on disk, what matters is the extension of - the file. Based on the extension, Biome will use the appropriate tool. + the file. Based on the extension, Biome knows how to lint the code. + Example: `echo 'let a;' | biome lint --stdin-file-path=file.js` -h, --help Prints help information ```