-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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(error-reporting): improve clarity for opt-out folks #3876
Conversation
lighthouse-cli/cli-flags.js
Outdated
@@ -59,7 +59,7 @@ function getFlags(manualArgv) { | |||
'Configuration:') | |||
.describe({ | |||
'enable-error-reporting': | |||
'Enables error reporting (prompts once by default, setting this flag will force error reporting to that state).', | |||
'Force enables error reporting. --no-enable-error-reporting will force disable. More: https://git.io/vFFTO', |
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.
"Force enables" sounds like a Jedi move. How about "Enables error reporting, overriding any saved preference...."
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.
Enables error reporting, overriding any saved preference. --no-enable-error-reporting will do the opposite. More: https://git.io/vFFTO
should we never prompt again or after x weeks or after each new release? |
I'm into the idea of prompting again if we hit that 20sec timeout, but also it may not matter with enough scale. |
Should we ship a quick 2.6.1 with this and Brendans new PR? |
fixes #3854