You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our team has been struggling with Biome inconsistently formatting workspace files. On save, sometimes it uses the default biome settings, and sometimes it uses our biome.json settings. In addition, when pressing Ctrl + Shift + P, we are able to see a bunch of Biome formatters, which did not seem to be the case in previous versions.
Occasionally, restarting VSCode or closing out of the current file and reopening seems to fix it, but not consistently as well.
Steps to reproduce
Attempt to format a file (potentially in a large monorepo which has biome.json's that depend on each other, but may be unrelated)
See that the formatting is inconsistent.
Expected behavior
The formatting was consistent in Biome 1.7.0, but after we updated to 1.9.3, the formatting has not been consistent at all.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Link to a minimal reproduction
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
VS Code version
1.93.1
Extension version
2.3.0
Biome version
1.9.3
Operating system
Description
Our team has been struggling with Biome inconsistently formatting workspace files. On save, sometimes it uses the default biome settings, and sometimes it uses our biome.json settings. In addition, when pressing Ctrl + Shift + P, we are able to see a bunch of Biome formatters, which did not seem to be the case in previous versions.
Occasionally, restarting VSCode or closing out of the current file and reopening seems to fix it, but not consistently as well.
Steps to reproduce
Expected behavior
The formatting was consistent in Biome 1.7.0, but after we updated to 1.9.3, the formatting has not been consistent at all.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Link to a minimal reproduction
No response
Logs
No response
The text was updated successfully, but these errors were encountered: