Environment information
CLI:
Version: 1.8.3
Color support: true
Platform:
CPU Architecture: x86_64
OS: linux
Environment:
BIOME_LOG_DIR: unset
NO_COLOR: unset
TERM: "xterm-256color"
JS_RUNTIME_VERSION: "v22.6.0"
JS_RUNTIME_NAME: "node"
NODE_PACKAGE_MANAGER: unset
Biome Configuration:
Status: unset
Workspace:
Open Documents: 0
What happened?
- Use a index.ts file with unsorted imports, and necessary formatting
- run
biome format index.ts -> see diff output
- run
cat index.ts | biome format --stdin-file-path=file.ts -> see the result of that diff in standard output
- try the previous two steps with
check instead of format -> The first output is as expected. But the pipe output makes no sense! It is one part original (unchanged) standard output, and second part the previous format diff.
Expected result
To get just the standard output of both diffs applied.
I am using the biome format --stdin-file-path to format code in helix for a while, this works well. But I tried to add also import sorting today. And to have that working, I would expect to just change the word format to check and get the same standardized output when providing the --stdin-file-path - the official docs say the same.
https://biomejs.dev/reference/cli/#biome-check -> the --stdin-file-path looks the same in both check and format, but only in format you get an output that is usable for the LSP.
Code of Conduct
Environment information
What happened?
biome format index.ts-> see diff outputcat index.ts | biome format --stdin-file-path=file.ts-> see the result of that diff in standard outputcheckinstead offormat-> The first output is as expected. But the pipe output makes no sense! It is one part original (unchanged) standard output, and second part the previous format diff.Expected result
To get just the standard output of both diffs applied.
I am using the
biome format --stdin-file-pathto format code in helix for a while, this works well. But I tried to add also import sorting today. And to have that working, I would expect to just change the wordformattocheckand get the same standardized output when providing the --stdin-file-path - the official docs say the same.https://biomejs.dev/reference/cli/#biome-check -> the
--stdin-file-pathlooks the same in both check and format, but only in format you get an output that is usable for the LSP.Code of Conduct