It looks good, please also consider lowercase everything. -- Matthieu Baechler
> Le 15 déc. 2015 à 18:21, Benoit Tellier <[email protected]> a écrit : > > Hi, > > Today I want to raise an issue : > > - It is nearly impossible to read James CLI help message > - James CLI command line naming is obscure, too long and too monolitic > > Having a lot of commands does not seem bad to me, but they should be > organised better than just grouped all together. > > > > I think something like : > > james-cli.sh DOMAIN ADD toto.org > james-cli.sh DOMAIN LIST > james-cli.sh DOMAIN REMOVE > > will be better than > > james-cli.sh ADDDOMAIN toto.org > james-cli.sh LISTDOMAIN > james-cli.sh REMOVEDOMAIN toto.org > > It will get even better with "cryptic" commands like : > > james-cli.sh ADDADDRESSMAPPING user domain fromAddress > > would be : > > james-cli.sh MAPPING ADDRESS ADD user domain fromAddress > > The global syntax I propose is : > > james-cli.sh FUNCTIONNALITY [EXTRA SPECS...] COMMAND [ARGS... ] > > > > On the help display it might help as : > > - Related commands will be grouped together, CLRF isolated from other > groups > - We can add a help message to explain the functionality > - As they are space separated, command names will get easier to read > > > If peoples thinks this might help, I am motivated to : > > - 1/ open a jira issue > - 2/ code this up (this seems not that complicated) > > And of course, if you have feedbacks, you will be very welcome. > > Benoit > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
