-
Notifications
You must be signed in to change notification settings - Fork 22
Fix --dump-test-list #266
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
base: main
Are you sure you want to change the base?
Fix --dump-test-list #266
Conversation
✅ Deploy Preview for webkit-jetstream-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
As a follow-up I should still implement a proper cli tests that parses the output for --dump-test-list and --help |
danleh
left a comment
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 with question / optional rejection of the startsWith('--no') change.
| } | ||
| let value = parts.slice(1).join("="); | ||
| if (flagName === "no-prefetch") value = "false"; | ||
| if (flagName.startsWith("no-")) value = "false"; |
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.
Do we have some other parameter that uses this --no prefix? Or rather: all other boolean parameters are set to false by default, whereas prefetchResources is true, right? So maybe don't generify this just yet, since supplying, e.g., --no-ramification does nothing, right?
We moved the params parsing partially to the Params which was not use in cli.js
Directly use the cli-only arguments in cli.js instead.