Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Adding biome.jsonc to .gitignore completely breaks the extension #520

Closed
2 of 3 tasks
SirzBenjie opened this issue Mar 8, 2025 · 2 comments
Closed
2 of 3 tasks
Labels
Needs reproduction Needs a reproduction Triage

Comments

@SirzBenjie
Copy link

VS Code version

1.98.0 6609ac3d66f4eade5cf376d1cb76f13985724bcb x64

Extension version

2.3.2 AND 2025.2.72227

Biome version

1.9.4

Operating system

  • Windows
  • macOS
  • Linux

Description

This title is pretty self explanatory. Biome will break if you add its configuration file to .gitignore. Or, at least, it did for me.

Steps to reproduce

In biome.jsonc (I didn't test whether this issue happens with biome.,json as well), make sure you have VCS enabled:

"vcs": {
    "enabled": false,
    "clientKind": "git",
    "useIgnoreFile": true
}

Then, make any file that you want to be formatted/linted/whatever with vscode.

When you try to format, vscode will give you the error "biome is configured as your default formatter but isn't able to handle filetype files.

Expected behavior

The extension shouldn't break if biome.jsonc is added to .gitignore

Does this issue occur when using the CLI directly?

Not sure / Not applicable

Link to a minimal reproduction

No response

Logs


@SirzBenjie SirzBenjie changed the title 🐛 Adding biome.json to .gitignore completely breaks the extension 🐛 Adding biome.jsonc to .gitignore completely breaks the extension Mar 8, 2025
@ematipico ematipico added the Needs reproduction Needs a reproduction label Mar 8, 2025
@ematipico
Copy link
Member

ematipico commented Mar 11, 2025

Can you please create a reproduction.

What are the contents of the ignore file? Does the CLI work?

Copy link
Contributor

This issue has been automatically closed because it has been inactive for more than 3 days and it does not have a minimal reproduction.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs reproduction Needs a reproduction Triage
Projects
None yet
Development

No branches or pull requests

2 participants