How to properly use command syntax about adr HOT 4 CLOSED

Hi, @MathieuLavigneCC it's same, and it's also some in my macbook. I could be a bug. Have you try those from source code.

.option('-n', 'create new ADR', create)
.command('new <title>')
  .description('create new ADR')
  .action(create)

if it works, you can just make a PR. I don't have a Ubuntu machine

from adr.

It's OK to only create Title1 for adr -n Title1 Title2

And then you can also delete option syntax.

from adr.

Yes it works, I use it as a workaround.
OK, let's go for a PR !

from adr.

I am working on the PR and here are some use cases I would like to share with you.

Using this syntax :

adr -n Title1 Title2

Creates only "Title1" adr file and not "Title2". How about you ?

It feels like this is not the proper way to use commander lib. You may not agree. I am wondering if this option syntax (a single "n" with a dash) is appropriate ? Maybe the command syntax is better suitable. For instance this syntax :

adr -n Title1 Title2

Should be deleted and replaced by :

adr new Title1 Title2

For all commands (new, list, update, etc...). May I delete every option syntax and replace them with command syntax ?

from adr.