-
Notifications
You must be signed in to change notification settings - Fork 1
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
"error: unknown option" in versions later than 0.5.4 #5
Comments
Interesting. I've confirmed this. Thanks for the report. From what I can tell, this was due to changes in the Passing args to the jobs file was never an intended feature. In fact, they don't really get forwarded; it's just that the jobs file gets loaded into the same node process, so it can see the same args. That, and This is a bit tricky to "fix" because, in theory, job names can look like options. So, in your example, there might be a job named |
(Separately, I noticed that the commander upgrade seems to have also broken other options, and I have a fix for that.) |
Ok, I've published a new version of |
Ah okay - thanks for explaining that. I wasn't aware of the mechanics of it. I do think the ability to pass options to the new Node processes is a very useful feature for But yes, 0.5.10 fixed the issue on my end. I did notice before that it always recognized anything prefixed with Thanks for updating and for continuing to support this package, Jeff! |
Glad to hear this fixes the issue for you! I'm curious how you've been using |
Well, you could say that you know the details better than I do, since I've only recently joined the Prep team at Tableau =D |
Ah, I see. That's why I didn't recognize your name. Thanks for carrying on the Prep mission at Tableau! |
In version 0.5.4, args passed like
jr dev -x
, for example, are forwarded tojobs.js
so they can be passed to scripts, but in every later version all args yielderror: unknown option '-x'
.The text was updated successfully, but these errors were encountered: