fix: allow nested biome.json without explicit root field #8520
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.
Summary
Fixed the
nested root configurationerror that was incorrectly reported when a subdirectory contained abiome.jsonfile without an explicitroot: truefield.When a project had a
biome.jsonin a subdirectory (e.g.,web/biome.json) with just partial configuration, Biome would report:✖ Found a nested root configuration, but there's already a root configuration.
This PR fixes the behavior by:
root: truewas explicitly set in the source file (beforeapply_extendstransforms the config)root: falsefor nested configs without explicitrootfield to prevent them from being treated as root configurationsrootnorextendsis setFixes #7942
Test Plan
Existing tests pass:
should_fail_for_nested_roots- no longer errorserrors_on_ignored_nested_biome_json- no longer errors