Native argument parsing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No source files or tests are named. Start by reading the docopt-style example and the proposed lj docstring invocation, then define the language and CLI behavior needed for both built-in argument parsing and docstring generation. Done requires an agreed design covering syntax, generated values, imports or configuration, and the command-line workflow.
Written by the indexing model from the issue text.
Description
Argument parsing is so common that it should be built into the language. For example Docopt Strings should be automatically recognized. This should not require imports or configuration in the code by the user. They should be responsible for the docstring and that is all. Remembering the syntax and symantics of docstring itself can also be tedious. LJ should provide a command line tool that aids in generating this string.
Examples
"""
Hello, world!
Usage:
hello_world <author>
hello_world -h | --help
hello_world --version
Options:
-h --help Show this screen.
--version Show version.
"""
main() {
printf("Hello, world!, from %s", author)
}
This example uses multi line comment syntax similar to docstrings in python. This is just for the purpose of the example. This example also demonstrates the author variable being in scope due to the docstring. This is also just for the purpose of the example. We may want to explore having an implicit arg map or similar.
$ lj docstring --name "Hello,world!" hello_world <author>
$ ... #print docstring shown in previous example
This cli would need to be easy enough to use that a user wouldn't need to google docopt everytime they need to do some argument parsing.
- Dominant language
- Java
- Stars
- 6
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from JMU-CS/less-java
-
cleanup help wanted
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
cleanup
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
cleanup enhancement
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
cleanup
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Add REPL Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in JMU-CS/less-java
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Two open-case totals on one screen: the Programs tile says 15,858 and the nav badge says 15,868 Openbug frontend maui-pilot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/eo-graphs#74 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100