-
Updated
Mar 18, 2022 - Rust
command-line-parser
Here are 278 public repositories matching this topic...
-
Updated
Mar 16, 2022 - Java
-
Updated
Feb 27, 2022 - TypeScript
-
Updated
Mar 6, 2022 - Kotlin
-
Updated
Mar 1, 2022 - C++
-
Updated
Mar 17, 2022 - Scala
I guess there is no real consistent scheme, but quite a few tools capitalize the help section headers.
So maybe a flag could be added to do the same when using kotlin-argparser.
So showiing
Usage: [-h] [-a] IMAGE-DIRECTORY MARKDOWN-FILES...
Optional arguments:
-h, --help show this help message and exit
-a, --auto Automatically remove orphan images
Position
Apparently GoDoc cannot show documentation for exported methods of un-exported structs, and it makes no sense to export parser
and/or command
, thus this project should provide its own documentation page.
Add more examples
-
Updated
Nov 8, 2021 - Ruby
-
Updated
Feb 2, 2022 - C++
-
Updated
Feb 21, 2022 - Clojure
-
Updated
Jul 16, 2021 - Kotlin
-
Updated
Jan 4, 2019 - Objective-C
-
Updated
Aug 8, 2020 - TypeScript
-
Updated
Jan 21, 2021 - C++
-
Updated
Mar 10, 2022 - C#
-
Updated
Nov 21, 2020 - Swift
-
Updated
Jan 8, 2022 - Shell
-
Updated
Dec 30, 2020
-
Updated
Mar 6, 2022 - Julia
-
Updated
Jan 25, 2021 - C++
-
Updated
Jan 18, 2022 - TypeScript
-
Updated
Jul 26, 2021 - C#
-
Updated
Mar 12, 2022 - Go
-
Updated
Feb 13, 2022 - C++
-
Updated
Jan 20, 2022 - Common Lisp
-
Updated
Apr 24, 2019 - C#
-
Updated
Jan 2, 2018 - Nim
-
Updated
Mar 15, 2022 - Go
Improve this page
Add a description, image, and links to the command-line-parser topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the command-line-parser topic, visit your repo's landing page and select "manage topics."
I know it's really an edge case since it can only happen when not reading the awesome documentation properly.
But since it's actually a contradiction according to the documentation and other similar things are also throwing an error, you might want to consider checking for this case and throwing an INVALID_DEFINITIONS error?
Alternatively it would make sense to just document which one wins,