chore(deps): update dependency @biomejs/biome to v1.8.2 #397
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.8.1
->1.8.2
Release Notes
biomejs/biome (@biomejs/biome)
v1.8.2
Compare Source
CLI
Bug fixes
biome migrate
and thus choke the parser. Contributed by @Sec-antEnhancement
Reword the reporter message
No fixes needed
toNo fixes applied
.The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:
The new message suits better in these cases.
Contributed by @Sec-ant
Configuration
Bug fixes
Don't conceal previous overrides (#3176).
Previously, each override inherited the unset configuration of the base configuration.
This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.
For example, in the next example,
noDebugger
was disabled for theindex.js
file.The rule is now correctly enabled for the
index.js
file.Contributed by @Conaclos
Formatter
Bug fixes
JavaScript APIs
Bug fixes
v1.8.0
Linter
New features
Bug fixes
Add nursery/noShorthandPropertyOverrides. #2958 Contributed by @neokidev
Fix [#3084] false positive by correctly recognize parenthesized return statement. Contributed by @unvalley
useImportExtensions now suggests a correct fix for
import '.'
andimport './.'
. Contributed by @minht11Fix useDateNow false positive when new Date object has arguments
new Date(0).getTime()
. Contributed by @minht11.The
noUnmatchableAnbSelector
rule is now able to catch unmatchablean+b
selectors like0n+0
or-0n+0
. Contributed by @Sec-ant.The
useHookAtTopLevel
rule now recognizes properties named as hooks likefoo.useFoo()
. Contributed by @ksnyder9801Fix #3092, prevent warning for
Custom properties (--*)
. Contributed by @chansukeFix a false positive in the
useLiteralKeys
rule. (#3160)This rule now ignores the following kind of computed member name:
Contributed by @Sec-ant
The noUnknownProperty rule now ignores the
composes
property often used in css modules. #3000 Contributed by @chansukeFix false positives of the useExhaustiveDependencies rule.
The component itself is considered stable when it is used recursively inside a hook closure defined inside of it:
Also,
export default function
andexport default class
are considered stable now because they can only appear at the top level of a module.Contributed by @Sec-ant
Fix missing
withDefaults
macro in vue files for globals variables. Contributed by @Shyam-ChenParser
Bug fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.