Replies: 2 comments 2 replies
-
I don't understand the proposal, sorry.
|
Beta Was this translation helpful? Give feedback.
-
I think I might lean towards a simple
It's probably disabled for a reason in the config, so assuming it should be overridden might be a bit of a leap. But it is true the user might just want to experiment or format/lint something specifically, and it's annoying if you are required to update the config for that. |
Beta Was this translation helpful? Give feedback.
-
While I was working on #2860, I noticed that
biome format
andbiome lint
don't run the formatter / the linter when they are disabled in the configuration.For instance, given the following configuration:
The following commands don't execute the formatter and the linter.
Unlike these commands,
biome check
allows overridinglinter>enabled
andformatter.enabled
using the corresponding CLI option.With the same configuration, a user can force the execution of the formatter and the linter:
❯ npx biome check --formatter-enabled=true --linter-enabled=true .
Note that this doesn't override
overrides
. Thus, the formatter and the linter are still disabled for files under the dist directory.I don't think we should add the
--formatter-enabled
and--linter-enabled
on thebiome format
and thebiome lint
commands. Instead, we could consider that they are implied.If a user execute
biome format
/biome lint
, I think it is fair to assume that the user wants to enable the formatter/the linter.Beta Was this translation helpful? Give feedback.
All reactions