-
The current help is fine but could be better (the code as well, that is a mess, but contained 😅). Here an idea to better visualise nested commands with ASCII lines:
```shell
Litr - Language Indepe…
-
There are async tests failing with no obvious reason behind. A `@todo` comment was placed here: https://github.com/krieselreihe/natr/blob/master/src/__tests__/duplex-stream.test.js#L36
The followin…
-
## Description
Given the following configuration:
```toml
[commands]
[commands.update]
script = "git pull && git fetch --prune && yarn"
description = "Update this repository."
[commands.o…
-
The tool should be easy to install, so it needs to be published where possible to be available for easy install, e.g. brew, apt, etc.
-
Currently the special parameter `-h` / `--help` does nothing. Goal is that this will print a beautiful auto generated help text inside the terminal.
Reference material:
- http://docopt.org/
- htt…
-
Scanning and Parsing the command line arguments should return descriptive, helpful errors for a user. The current errors are vague and sometimes not explicit enough.
-
As seen in https://github.com/krieselreihe/litr/wiki/Setup#example variables can be used with `${...}` inside scripts
## Open questions
* What syntax should be used / is `${...}` really a good c…
-
```shell script
litr --help # Show litr help
litr -h # Show litr help
litr build # Exec command "build"
litr bui…
-
Errors produced by https://github.com/ToruNiina/toml11 need to be parsed/wrapped to be more helpful and guiding for a user. Also, the internal mechanics shall not be put to the user (e.g. "What if the…
-
## Goal
The only not user defined Litr call should be `litr --help` to show the help text. The help text should be as user friendly as possible and give some meaningful information even on a minima…