-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
core: deprecate passes, remove config navigations from FR #13881
Conversation
types/config.d.ts
Outdated
id: string; | ||
/** Whether throttling settings should be skipped for the pass. */ | ||
disableThrottling?: boolean; | ||
/** Whether storage clearing (service workers, cache storage) should be skipped for the pass. A run-wide setting of `true` takes precedence over this value. */ | ||
disableStorageReset?: boolean; | ||
/** The array of artifacts to collect during the navigation. */ | ||
artifacts?: Array<string>; |
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.
I didn't add any of these settings to config.settings
because:
disableStorageReset
is already onconfig.settings
id
doesn't make sense if there is only one navigationdisableThrottling
can be achieved withconfig.settings.throttlingMethod = 'provided'
config.artifacts
is now the canonical list of artifacts, we don't need to maintain a second one
@@ -98,7 +98,6 @@ const defaultConfig = { | |||
{id: artifacts.EmbeddedContent, gatherer: 'seo/embedded-content'}, | |||
{id: artifacts.FontSize, gatherer: 'seo/font-size'}, | |||
{id: artifacts.Inputs, gatherer: 'inputs'}, | |||
{id: artifacts.FullPageScreenshot, gatherer: 'full-page-screenshot'}, |
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.
This is actually a minor bug fix for timespan/snapshot because they weren't doing FPS as the final gatherer before.
This has more changes than I was picturing. I thought we were talking about moving the new That would allow basically everything else to remain as it is today. More stuff to maintain, but fewer additional changes to get right before 10.0, leaves the door open to changing our mind on ditching passes, smoke tests still work, etc. |
That's what I was looking into originally, the problem is what to do with the extra settings defined on each pass. It would leave |
Can you give more specifics? Since it's only the config input, it seems like it wouldn't matter.
Yeah, but passes will be in a weird half-deprecated state so that just matches what we're doing :) |
We would be telling users that |
Oh, I thought we were discussing removing |
Ok I think I was confused and got turned around. You don't have an issue with adding the pass settings to |
lighthouse-core/test/fraggle-rock/gather/navigation-runner-test.js
Outdated
Show resolved
Hide resolved
@brendankenny @connorjclark this should be ready for review |
As discussed here, this PR removes config navigations (known as passes in legacy mode) from FR navigations.
There are some settings which are only configurable on a legacy pass/config navigation (e.g.
pauseAfterFCPMs
). I think it's better to define these onconfig.settings
rather than maintain them in a half-deprecated state onconfig.passes
.