Closed waldyrious closed 1 year ago
Agree there is a bit of inconsistency. I think usually there is short form for commonly used flags, so may not be applicable for all. But I definitely agree this could be improved.
Taken onboard your comments, however left completion flags as is, at the moment xc uses an external completion lib, so will need to refactor that into xc to have more control.
Sure, thanks! I've submitted #65 for additional consistency in the option descriptions.
By the way, do you have any thoughts about the suggestion I made above to make xc support formats other than markdown? I could create a separate issue to track that if it's something you'd consider.
Thanks! We can keep a ticket open for other formats, but at this point I think sticking to markdown and getting it working well with that format is where I want to work on for the time being.
Cool, makes sense. I've opened #66 to track that.
Most options of the CLI have both a short and a long version. Notable exceptions are
-version
, which only has a long version, and-y
, which only has a short one. For consistency, these two could have both variants.Here's what I'd suggest:
-V
as the short variant of-version
(since -v is often used for--verbose
)-noprompt
as the long variant of-y
Additionally, perhaps consider changing
-md
to-n
/-dry-run
, since the format of the task definition document should not be relevant — i.e., it should be possible to eventually makexc
support AsciiDoc, reStructuredText, and other lightweight markup formats.