-
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
docs: update stale references to audits #9760
Conversation
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.
nice catch! not sure what spurs it now though :)
docs/readme.md
Outdated
@@ -94,7 +94,7 @@ In order to extend the Lighthouse configuration programmatically, you need to pa | |||
'first-meaningful-paint', | |||
'speed-index-metric', | |||
'estimated-input-latency', | |||
'first-interactive', | |||
'first-cpu-idle', | |||
'consistently-interactive', |
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.
should probably update consistently-interactive
, speed-index-metric
, and kill estimated-input-latency
if we're updating these now, or could just wait for when we really kill EIL :)
the golden lantern file has refernces to |
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.
LGTM w/that change
if we're updating should we just update to be consistent with the planned 6.0 set so we don't have to update again? They're just examples, doesn't seem like we're losing anything if we don't keep EIL around until it's removed |
missed these in #4982