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.

Sign up for GitHub

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

Jump to bottom

Remove support for arbitrary extension for --config-path and BIOME_CONFIG_PATH. We should handle only .json and .jsonc and emit an error otherwise. #4942

Closed
Tracked by #3727
ematipico opened this issue Jan 22, 2025 · 0 comments · Fixed by #4944
Closed
Tracked by #3727

Remove support for arbitrary extension for --config-path and BIOME_CONFIG_PATH. We should handle only .json and .jsonc and emit an error otherwise. #4942

ematipico opened this issue Jan 22, 2025 · 0 comments · Fixed by #4944
Assignees
@ematipico

Comments

@ematipico
Copy link
Member

ematipico commented Jan 22, 2025 •
edited
Loading

At the moment, a command like the following is accepted:

biome --config-path=file.yml

The file.yml gets interpreted as a JSON/JSONC file, which is incorrect. The task is to reject such cases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ematipico ematipico

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(core): raise an error when invalid config extension is passed biomejs/biome
1 participant
@ematipico