Roo Commands max, instead, number, figure

amy

roogt; field string code --notNull --sizeMin 1 --sizeMax 30
Why must we type --sizeMin and --sizeMax instead of --min and --max ? It can figure out that if the field type is string then it's a size/length value instead of numeric.

roogt; field number somePercent --type java.lang.Integer --min 0 --max 100
Why must we type quot;numberquot; and quot;--type java.lang.Integerquot; instead of simply typing quot;intquot; for the field type? (and the other numeric types). You can still have this verbose style to allow for numeric types that don't have a shorthand (either because they are new or they are rarely used).

roogt; field string code --notNull --sizeMin 1 --sizeMax 30
roogt; field number somePercent --type java.lang.Integer --min 0 --max 100
What's with the double-dash for parameters? Are you making some shorter versions with a single-dash or something? Why not drop the dashes completely? How about:

roogt; field string code notNull min 1 max 30
roogt; field string code notNull range 1,30
roogt; field int somePercent min 0 max 100
roogt; field int somePercent range 0,100
Or, if some sort of quot;this one's paired with the otherquot; is desired:
roogt; field string code notNull min:1 max:30

roogt; perform command --mavenCommand some:command
How about instead we do quot;mvnquot; ? I won't ever use that feature. I can alt+tab from Eclipse (or the Roo console) to a console and type quot;mvn do:nowquot; faster than clicking into the Roo console and typing that long command.

It seems the Roo console was written with a very verbose typing scheme. Tab completion cannot speedup quot;perform command --mavenCommandquot; to compete with quot;mvnquot;.