parseNumber and parseBoolean

[jmcdo29]

How would the community feel about adding in methods for parseBoolean and parseNumber so that they didn't have to write them themselves?

The parseBoolean() could go so far as to accept yes, y, 1, t, and true for true values, and no, n, 0, f and false for false values.

Anyone have any thoughts about it?

[smolinari]

As we were discussing, having/ using inquirer for input would be really cool. Also a coloring utility and ora too for enhancing output. Oh yeah! :)

Scott

[micalevisk]

that would be useful.

How would the interface looks like? They will belong to which class?

[jmcdo29]

Right. They'll need a custom token for it and to add in the provider, but it would be doable

[micalevisk]

any cons on using InquirerService, and
parseNumber(val: string | undefined, opts?: { promptIfMissing:boolean }): number
parseBoolean(val: string | undefined, opts?: { promptIfMissing:boolean }): boolean

parsing + prompt might be pretty common. Other stuffs (like coloring and spinners) could be added later on under opts object

[micalevisk]

maybe CLIParsersService would be better for SoC principle

[smolinari]

I'd say, v2 is the better one.

Scott

[jmcdo29]

Added #251 to address this