No way to specify optional flags about cli HOT 5 CLOSED

Michael, I'll ask @tedsuo to help with this.

from cli.

Hi @fraenkel,
You can see the story in the CLI public backlog here.

@thansmann &@caseymct

from cli.

I have a pull request ready for codegangsta to see if he will add an IsSet method. scottruitt --- Re: [cli] No way to specify optional flags (#38) --- From:"scottruitt" [email protected]"cloudfoundry/cli" [email protected]"Michael Fraenkel" [email protected]:Wed, Dec 18, 2013 10:32 AMSubjectRe: [cli] No way to specify optional flags (#38)Michael, I'll ask @tedsuo to help with this.

—Reply to this email directly or view it on GitHub.

from cli.

@fraenkel so we just hit this issue as well. Our solution was to change the flag type from int to string, so that we can differentiate between not set (empty string) and "0".

see the commit for an example: 03e790b

Hope your pull request goes through with codegansta, it would be a good feature.

from cli.

Yea, that doesn't work for me since I have a Bool I can't use String since -enabled won't be handled properly. I was also hoping that I could play another trick and use String but have the parse treat it as a Bool with the magic IsBoolFlag, but they first type assert to boolValue which stops me dead in my tracks.

As an aside, there are a few other cases that need the Int -> String trick above, e.g., Buildpack position.

from cli.