You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The link in question documents a feature that is not yet part of a stable release. This just tripped me up, as it describes a feature that I need, and I'm using the latest release, but the recommended config is failing to validate.
It'd be fine if the docs included pre-release functionality, provided that the portion of the docs that reflect items that aren't in the stable build were flagged as pre-release. Unfortunately, at the top of the page it indicates that the feature has been available Since: v1.8.0, which is especially misleading when portions of the page describe enhancements that haven't been released yet.
Expectations
The docs page would either describe the latest stable release, or in cases when details about pre-release functionality are included, there would be some indication that the functionality in question is only available via a pre-release/nightly build.
Code of Conduct
I agree to follow Biome's Code of Conduct
The text was updated successfully, but these errors were encountered:
Documentation URL
https://biomejs.dev/linter/rules/use-import-extensions/#options
Description
The link in question documents a feature that is not yet part of a stable release. This just tripped me up, as it describes a feature that I need, and I'm using the latest release, but the recommended config is failing to validate.
It'd be fine if the docs included pre-release functionality, provided that the portion of the docs that reflect items that aren't in the stable build were flagged as pre-release. Unfortunately, at the top of the page it indicates that the feature has been available
Since: v1.8.0
, which is especially misleading when portions of the page describe enhancements that haven't been released yet.Expectations
The docs page would either describe the latest stable release, or in cases when details about pre-release functionality are included, there would be some indication that the functionality in question is only available via a pre-release/nightly build.
Code of Conduct
The text was updated successfully, but these errors were encountered: