-
Notifications
You must be signed in to change notification settings - Fork 49
feat: pass cli arguments not used by opennext to wrangler #720
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?
Conversation
🦋 Changeset detectedLatest commit: efda97e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
Co-authored-by: Victor Berchet <victor@suumit.com>
if (name && !(name in options)) { | ||
passthroughArgs.push(args[i]!); | ||
|
||
while (!args[i + 1]?.startsWith("-")) { |
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.
Thanks for the update.
I find the new version much more readable.
Still wondering why we have a while here.
I get the --flagName flagValue
thing but why more strings after flagValue
?
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 was assuming array arguments might be able to be provided without specifying the key each time, e.g. --flagName flagValue1 flagValue2
. yargs calls it greedy arrays - https://github.com/yargs/yargs-parser/blob/main/README.md#greedy-arrays
No description provided.