-
-
Notifications
You must be signed in to change notification settings - Fork 688
fix(core): ignore nested configs #6662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: 2c8d765 The changes in this PR will be included in the next version bump. This PR includes changesets to release 13 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for looking into this! We should update our docs and provide an example for this use case, and while doing so, we should highlight the fact that this "feature" works only when the nested configurations are specified in files.includes
. Meaning that VCS ignore files aren't taken into consideration
CodSpeed Performance ReportMerging #6662 will not alter performanceComparing Summary
|
b903dc0
to
1876202
Compare
I've pushed a docs update to biomejs/website#2604 |
Summary
Fixes #6509.
If a nested configuration file is ignored by the root configuration, it will now actually be ignored.
Biome has an exception in place for configuration files so they cannot be ignored, because the configuration files are vital to Biome itself. But this exception was incorrectly applied to nested configurations as well. Now only the root configuration is exempt from being ignored.
Additionally, I ran into quite a bit of a refactoring. I moved most of the implementation of
WorkspaceServer::file_features()
intoprojects.rs
, so that we can again save ourselves some cloning and unnecessary Papaya lookups. But it turned outWorkspaceSettingsHandle
was getting in the way of me doing that, so I had a hard look atWorkspaceSettingsHandle
itself. Turned out thatWorkspaceSettingsHandle
was entirely unnecessary, and the fact it wrapped settings in anOption
was unnecessary too. So I removedWorkspaceSettingsHandle
and a lot of places that used to passOption<&Settings>
now pass a plain&Settings
.Test Plan
Test added and snapshots updated.
You may notice that for some snapshots, the amount of files checked has decreased by one. These are nested configuration files that were checked before, where this behaviour is unexpected with the new logic.