Do not raise an error if the language of the file extension cannot be determined

[smorimoto]

As the title says, it currently raises an error if the language of the file extension cannot be determined, but it should be either warning or info.

[smorimoto]

Although the log shows it as warning, it somehow ended up being reported as error, and the exit code is also set as error 🤷‍♂️

xxxx files/missingHandler ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Biome could not determine the language for the file extension ml
  

The number of diagnostics exceeds the number allowed by Biome.
Diagnostics not shown: 161.
Compared 81 file(s) in 11ms
format ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Some errors were emitted while running checks.

❯ echo $status
1

[ematipico]

Diagnostics not shown: 161.

There are 161 diagnostics. Are you sure that all 161 aren't errors?

[smorimoto]

Perhaps the lack of support for nested ignore files caused too many errors, most of which were not printed in the log, causing confusion.

[Conaclos]

You can set files.ignoreUnknown to true or the CLI option files-ignore-unknown=true top ignore unknown extensions.

[smorimoto]

Warning seems correct behaviour, but is getting an error correct?

[Conaclos]

No I think there is an issue there. I will turn the discussion into an issue.

[smorimoto]

Thanks a lot!

[EvHaus]

Is there a reason "ignoreUnknown": true isn't the default? Seems weird to me for Biome to be (by default) complaining about files it can't parse.

[ematipico]

Is there a reason "ignoreUnknown": true isn't the default? Seems weird to me for Biome to be (by default) complaining about files it can't parse.

This was the default behaviour since the beginning.

Since Biome (formerly Rome), was designed to be a bundler and handle many kinds of files, it was supposed to warn users for extraneous files.

Happy to review the behaviour.

[Conaclos]

This should now be solved :)