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

Remove the requireConfiguration option #27

Closed
ematipico opened this issue Dec 7, 2023 · 0 comments · Fixed by #30
Closed

Remove the requireConfiguration option #27

ematipico opened this issue Dec 7, 2023 · 0 comments · Fixed by #30
Assignees
Labels
Enhancement Improves an existing feature Good first issue Help wanted External contributions are welcome

Comments

@ematipico
Copy link
Member

We discussed this internally, and we agreed that this option must go.

Biome can resolve its configuration perfectly fine, and if it doesn't, it uses the default behaviour.

The reason why we added this configuration was because "people don't want to see diagnostics if they aren't in a biome project". While this is true, this hides how powerful Biome is. People can still disable the extension if they need.

We want users to download the extension and start using it straightaway because that's what Biome is. Good defaults and configuration are not needed. This is the message we want to send.

@ematipico ematipico added Enhancement Improves an existing feature Help wanted External contributions are welcome Good first issue labels Dec 7, 2023
@nhedger nhedger self-assigned this Dec 7, 2023
@nhedger nhedger linked a pull request Dec 7, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improves an existing feature Good first issue Help wanted External contributions are welcome
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants