-
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(render-blocking): address followup feedback #5039
Conversation
requiredArtifacts: ['CSSUsage', 'URL', 'TagsBlockingFirstPaint', 'traces'], | ||
// This audit also looks at CSSUsage but has a graceful fallback if it failed, so do not mark | ||
// it as a "requiredArtifact". | ||
requiredArtifacts: ['URL', 'TagsBlockingFirstPaint', 'traces'], |
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 like this for working around gatherer errors, but won't this be undesirable if doing an --only-categories
/audits
? The CSSUsage
gatherer could be pruned. It won't be a failure but probably not what you want.
Time to introduce a desiredArtifacts
field? :D
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 also true. I have a slight preference for eliminating the failure case in exchange for making the onlyAudits: ['render-blocking-resource']
case a little more forgiving.
I'll add a todo to look into updating after an optionalArtifacts
:D
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.
Just to be clear, no changes then? (except for a TODO)
if so, sgtm :)
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
followup to #4995