Hi Eranda, Design-wise I'm more in favor of Design 2 where commands feel more natural (`<cmd> list exchange` as opposed to `<cmd> exchange list`). This would be a bit more complex to implement in terms of code, but IMO UX is better with design 2. This aligns to both WUM approach (which is a pattern most users expect from WSO2) and the widespread `kubectl` approach (It should be noted that AWS CLI implements commands similar to design 1).
Furthermore, when implementing helper commands like `help` and `version`, it might be better to duplicate WUM client designs as we need to provide a single experience for all WSO2 clients. WDYT? +1 for Go implementation. How are we planning to ship the CLI? Is it going to be a separate download? (if so, how would we ship updates for it?) From maintenance point of view, offloading most business logic to the REST API would be the better choice as a single version fo the CLI would be able to work with a range of server versions. Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Associate Technical Lead | WSO2 +94 77 220 7163 Blog: https://medium.com/@chamilad On Wed, Feb 7, 2018 at 3:51 PM, Dakshika Jayathilaka <[email protected]> wrote: > Hi All, > > IMO we need to support basic level features such as *--help*, *--version* > and *--verbose* on each CLI tool that we are building. > > Also, we need to think about the standard output for each scenario as > well. Shall we add few samples for that as well? > > Regards, > > *Dakshika Jayathilaka* > PMC Member & Committer of Apache Stratos > Associate Technical Lead > WSO2, Inc. > lean.enterprise.middleware > 0771100911 > > On Wed, Feb 7, 2018 at 10:24 AM, Eranda Rajapakshe <[email protected]> > wrote: > >> Hi Imesh, >> >> Yes, we are going to include help command into the client. Thanks for the >> reference, it looks interesting. >> >> Thanks, >> >> On Wed, Feb 7, 2018 at 10:13 AM, Imesh Chandrasiri <[email protected]> >> wrote: >> >>> Hi Eranda, >>> >>> A small clarification on the commands. Could these have a '--help' >>> command where the syntax and the usage of the command is printed? IMHO it >>> would benefit the user to figure out the command usage then and there >>> without having to read the documentation. This is a nice article[1 >>> <https://zapier.com/engineering/how-to-cli/>] on some UX views of a CLI. >>> >>> [1] - https://zapier.com/engineering/how-to-cli/ >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Eranda Rajapakshe* >> Software Engineer >> WSO2 Inc. >> Mobile : +94784822608 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
