I think Ma just made an example of the option naming style instead of the
subcommand.
I think it's a good idea to support both checkcompatibility and cc as
subcommands.
Daniel Qian <chanjars...@gmail.com> 于2019年11月5日周二 上午7:28写道：
> Hello Ma, found current cli style is <subcommand> <options>.
> So if we do --check-compatability then which subcommand should we use?
>
> Bin Ma <mabin1...@gmail.com> 于2019年11月5日周二 上午12:44写道：
> >
> > I recommend keeping the same as the current option naming style,
> > such as "-c", "-- check-compability "
> >
> >
> > Wishes & Regards
> > -------------------------------
> > Mabin
> >
> >
> >
> > Willem Jiang <willem.ji...@gmail.com> 于2019年11月1日周五 下午12:31写道：
> >
> > > I think we can support checkcompatibility and the short one cc at the
> same
> > > time.
> > > Any thoughts?
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Wed, Oct 30, 2019 at 10:37 AM Daniel Qian <chanjars...@gmail.com>
> > > wrote:
> > > >
> > > > I created an issue SCB-1555[1] to integrate oas-validator
> > > > compatibility check to toolkit cli.
> > > >
> > > > I suggest usage like this:
> > > > java -jar toolkit-cli-{version}.jar checkcompability
> > > > /path/to/openapiv3-1.yaml /path/to/openapiv3-2.yaml
> > > >
> > > > But the subcommand checkcompability is too long, maybe we can use a
> > > > abbr for it, such as cc?
> > > >
> > > > Any ideas?
> > > >
> > > > [1] https://issues.apache.org/jira/browse/SCB-1555
> > > > [2]
> > >
> https://github.com/apache/servicecomb-toolkit/blob/import-oas-validator/oas-validator/README.md#%E5%85%BC%E5%AE%B9%E6%80%A7%E6%A3%80%E6%9F%A5
> > > >
> > > > --
> > > > Daniel Qian
> > > >
> > > > 博客：https://segmentfault.com/u/chanjarster
> > > > github：https://github.com/chanjarster
> > >
>
>
>
> --
> Daniel Qian
>
> 博客：https://segmentfault.com/u/chanjarster
> github：https://github.com/chanjarster
>
