You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Sergey Antonov <an...@gmail.com> on 2019/01/11 11:05:17 UTC
Options naming format in control.sh utility.
Hi, Igniters!
I want discuss and define options naming format in our utilities. I found
two naming styles in CommandHandler class --excludeCaches and --skip-zeros.
I think we should unify it. At this moment almost all options have second
naming format. I am offering rename --excludeCaches to --exclude-caches and
define format for future options. How about linux like format i.e.
--word1-word2?
--
BR, Sergey Antonov
Re: Options naming format in control.sh utility.
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I think that it makes sense.
Regards,
--
Ilya Kasnacheev
вт, 22 янв. 2019 г. в 22:24, Sergey Antonov <an...@gmail.com>:
> Igniters, what do you think about this topic?
>
> пт, 11 янв. 2019 г. в 14:17, Sergey Antonov <an...@gmail.com>:
>
> > Sergey,
> >
> > Not quite, I meant:
> > - boolean argument: *--word1-word2*
> > - single value argument *--word1-word2 value*
> > - multiple values argument *--word1-word2 value1,value2*
> >
> > пт, 11 янв. 2019 г. в 14:12, Sergey Kozlov <sk...@gridgain.com>:
> >
> >> Sergey,
> >>
> >> Thanks for raising up the question.
> >>
> >> Did you mean following (?):
> >> - boolean argument: *--word1-word2*
> >> - single value argument *--word1-word2=value*
> >> - multiple values argument *--word1-word2=value1
> --word1-word2=value2*
> >>
> >>
> >> On Fri, Jan 11, 2019 at 2:05 PM Sergey Antonov <
> antonovsergey93@gmail.com
> >> >
> >> wrote:
> >>
> >> > Hi, Igniters!
> >> >
> >> > I want discuss and define options naming format in our utilities. I
> >> found
> >> > two naming styles in CommandHandler class --excludeCaches and
> >> > --skip-zeros.
> >> > I think we should unify it. At this moment almost all options have
> >> second
> >> > naming format. I am offering rename --excludeCaches to
> --exclude-caches
> >> and
> >> > define format for future options. How about linux like format i.e.
> >> > --word1-word2?
> >> >
> >> > --
> >> > BR, Sergey Antonov
> >> >
> >>
> >>
> >> --
> >> Sergey Kozlov
> >> GridGain Systems
> >> www.gridgain.com
> >>
> >
> >
> > --
> > BR, Sergey Antonov
> >
>
>
> --
> BR, Sergey Antonov
>
Re: Options naming format in control.sh utility.
Posted by Sergey Antonov <an...@gmail.com>.
Igniters, what do you think about this topic?
пт, 11 янв. 2019 г. в 14:17, Sergey Antonov <an...@gmail.com>:
> Sergey,
>
> Not quite, I meant:
> - boolean argument: *--word1-word2*
> - single value argument *--word1-word2 value*
> - multiple values argument *--word1-word2 value1,value2*
>
> пт, 11 янв. 2019 г. в 14:12, Sergey Kozlov <sk...@gridgain.com>:
>
>> Sergey,
>>
>> Thanks for raising up the question.
>>
>> Did you mean following (?):
>> - boolean argument: *--word1-word2*
>> - single value argument *--word1-word2=value*
>> - multiple values argument *--word1-word2=value1 --word1-word2=value2*
>>
>>
>> On Fri, Jan 11, 2019 at 2:05 PM Sergey Antonov <antonovsergey93@gmail.com
>> >
>> wrote:
>>
>> > Hi, Igniters!
>> >
>> > I want discuss and define options naming format in our utilities. I
>> found
>> > two naming styles in CommandHandler class --excludeCaches and
>> > --skip-zeros.
>> > I think we should unify it. At this moment almost all options have
>> second
>> > naming format. I am offering rename --excludeCaches to --exclude-caches
>> and
>> > define format for future options. How about linux like format i.e.
>> > --word1-word2?
>> >
>> > --
>> > BR, Sergey Antonov
>> >
>>
>>
>> --
>> Sergey Kozlov
>> GridGain Systems
>> www.gridgain.com
>>
>
>
> --
> BR, Sergey Antonov
>
--
BR, Sergey Antonov
Re: Options naming format in control.sh utility.
Posted by Sergey Antonov <an...@gmail.com>.
Sergey,
Not quite, I meant:
- boolean argument: *--word1-word2*
- single value argument *--word1-word2 value*
- multiple values argument *--word1-word2 value1,value2*
пт, 11 янв. 2019 г. в 14:12, Sergey Kozlov <sk...@gridgain.com>:
> Sergey,
>
> Thanks for raising up the question.
>
> Did you mean following (?):
> - boolean argument: *--word1-word2*
> - single value argument *--word1-word2=value*
> - multiple values argument *--word1-word2=value1 --word1-word2=value2*
>
>
> On Fri, Jan 11, 2019 at 2:05 PM Sergey Antonov <an...@gmail.com>
> wrote:
>
> > Hi, Igniters!
> >
> > I want discuss and define options naming format in our utilities. I found
> > two naming styles in CommandHandler class --excludeCaches and
> > --skip-zeros.
> > I think we should unify it. At this moment almost all options have second
> > naming format. I am offering rename --excludeCaches to --exclude-caches
> and
> > define format for future options. How about linux like format i.e.
> > --word1-word2?
> >
> > --
> > BR, Sergey Antonov
> >
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>
--
BR, Sergey Antonov
Re: Options naming format in control.sh utility.
Posted by Sergey Kozlov <sk...@gridgain.com>.
Sergey,
Thanks for raising up the question.
Did you mean following (?):
- boolean argument: *--word1-word2*
- single value argument *--word1-word2=value*
- multiple values argument *--word1-word2=value1 --word1-word2=value2*
On Fri, Jan 11, 2019 at 2:05 PM Sergey Antonov <an...@gmail.com>
wrote:
> Hi, Igniters!
>
> I want discuss and define options naming format in our utilities. I found
> two naming styles in CommandHandler class --excludeCaches and
> --skip-zeros.
> I think we should unify it. At this moment almost all options have second
> naming format. I am offering rename --excludeCaches to --exclude-caches and
> define format for future options. How about linux like format i.e.
> --word1-word2?
>
> --
> BR, Sergey Antonov
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com