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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@biomejs/[email protected]
Patch Changes
#7941
19b8280Thanks @Conaclos! - Fixed #7943. Rules'optionsare now properly merged with the inheritedoptionsfrom a shared configuration.This means that you can now override a specific option from a rule without resetting the other options to their default.
Given the following shared configuration:
{ "linter": { "rules": { "style": { "useNamingConvention": { "level": "on", "options": { "strictCase": false, "conventions": [ { "selector": { "kind": "variable", "scope": "global" }, "formats": ["CONSTANT_CASE"] } ] } } } } } }And the user configuration that extends this shared configuration:
{ "extends": ["shared.json"], "linter": { "rules": { "style": { "useNamingConvention": { "level": "on", "options": { "strictCase": true } } } } } }The obtained merged configuration is now as follows:
{ "extends": ["shared.json"], "linter": { "rules": { "style": { "useNamingConvention": { "level": "on", "options": { "strictCase": true, "conventions": [ { "selector": { "kind": "variable", "scope": "global" }, "formats": ["CONSTANT_CASE"] } ] } } } } } }#7969
425963dThanks @ematipico! - Added support for the Svelte syntax{@debug}. The Biome HTML parser is now able to parse and format the blocks:#7921
547c2daThanks @dyc3! - Fixed #7854: The CSS parser, withtailwindDirectivesenabled, will now parse@source inline("underline");.#7856
c9e20c3Thanks @Netail! - Added the nursery rulenoContinue. Disallowing the usage of thecontinuestatement, structured control flow statements such asifshould be used instead.Invalid:
Valid:
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]