No description
- Janet 100%
| bin | Update jell, sbb, and bundled niche | |
| bundle | Update jipper | |
| data | ||
| src | Move a def closer to use | |
| test | ||
| usages | Use position info to obtain failure form string | |
| .jell.jdn | ||
| .niche.jdn | ||
| batch-niche.janet | Report niche path used for batch testing | |
| COPYING.txt | ||
| niche.janet | Move a def closer to use | |
| README | ||
Usage: niche [<file-or-dir>...]
niche [--help|[-h[h[h[h]]]]]
niche [-v|--version]
Nimbly Interpret Comment-Hidden Expressions
Parameters:
<file-or-dir> path to file or directory
Options:
-h, --help show this output
-hh show background material
-hhh show tutorial
-hhhh show reference
-v, --version show version information
Configuration:
.niche.jdn configuration file
Example uses:
1. Create and run comment-hidden expression tests in `src/`
directory:
$ niche src
2. A configuration file (`.niche.jdn`) can be used to
specify paths to operate on and avoid spelling out paths
at the command line:
$ niche
3. `niche` can be used via `jeep`, `jpm`, etc. with some
setup. In a project's root directory, create a suitable
`.niche.jdn` file and a runner file in the project's
`test/` subdirectory. Then, in the case of `jeep`:
$ jeep test
Example `.niche.jdn` configuration file:
{# what to work on - file and dir paths
:includes ["src" "bin/my-script"]
# what to skip - file paths only
:excludes ["src/sample.janet"]}
Example runner file `test/trigger-niche.janet`:
# adjust the path as needed
(import ../niche) # niche.janet is in project root
(niche/main)