-
Notifications
You must be signed in to change notification settings - Fork 4
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
iterable parameter values not passed correctly into the command-line #171
Comments
You mean you're literally getting You can try your fix, but the join will return a single string, which will be stuffed into a single command-line argument (spaces and all), which is probably not the intention either. |
@o-smirnov yes I get everything with the square brackets. Below is what is displayed on the terminal;
I will give my suggested fix much thought and try my fix, I just thought about it from head without trying the implementation. The only problem is the square brackets and the '', so simms is not able to read the passed values.
|
It's definitely a bug, but I can't see it from the code. Could you add a print statement here: stimela/stimela/kitchen/cab.py Line 387 in 084b3ff
It should be the case that |
As I had thought earlier, the bug is in Line 308 of stimela/stimela/kitchen/cab.py. Instead of using the I have changed
Of-course I stand to be corrected if there is anything I missed/misleading with my suggestion. |
There seems to be a bug with the repeat policy for a cab input that can accept two options in the form of a list to be cast as
--option X --option Y
on the command line.I have defined a cab with a repeat policy of
repeat: repeat
as documented here but I get the output as[--option X] [--option Y]
.I suggest a fix on this line to perhaps something like
' '.join(list(itertools.chain.from_iterable([option, x] for x in value))) if option else list(value)
. This ensures that the correct output is passed into the command-line when multiple values (in list form) foroption
are provided.The text was updated successfully, but these errors were encountered: