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.
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(runner): asset manager helper #13519
core(runner): asset manager helper #13519
Changes from 6 commits
552fe50
739a058
48cf364
2f011d1
71c67e4
e32c855
972bf83
8abf951
7111b21
b8a2da3
d073017
07ef5d9
382886d
fac8b10
b7f53f0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Removing this check should be the only functional change to legacy mode. I didn't think it was needed because we can proceed with the
requestedUrl
from the artifacts. I'd be open to adding this back as a non-fatal warning or something in a different location.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.
The check makes more sense from the context of the CLI. Currently you can do
-G
and then-A
separately but you must use the same URL, otherwise it errors because you probably made a mistake. Perhaps instead, we should have-A
mode only use what is saved in the gathering step–url, settings, etc. and throw if a url is also providedThere 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 would prefer just logging a warning, since we could just ignore the passed in URL.
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'm fine with just a warning. -G/A is pretty advanced usage so we don't really need these runtime failures to protect us, IMO
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.
A report warning, then, not logger. This will otherwise be ignored and is sure to mess me up eventually so a loud warning is necessary :)
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 would prefer switching to a fatal error in the CLI than that. We would need to send the warning message all the way down to
Runner.run
where run warnings are collected. Removing URL checks fromRunner.run
is part of the reason I created this PR.The warning is quiet, but Lighthouse is still performing the more correct and expected operation IMO.