airsequel / oclis Goto Github PK

5.0 5.0 0.0 180 KB

The obvious CLI specification format. You define the spec, Oclis generates the code! Support for PureScript so far. PRs for more languages appreciated!

License: ISC License

Makefile 4.59% Nix 9.82% NCL 26.33% Rust 59.26%

argparse cli cli-spec docopt elm haskell nickel optparse optparse-applicative polyglot purescript rust specification

oclis's People

Contributors

Stargazers

Watchers

oclis's Issues

Add an ANSI art option a la Python's Typer

https://github.com/tiangolo/typer

$ python main.py --help

 Usage: main.py [OPTIONS] COMMAND [ARGS]...

╭─ Options ─────────────────────────────────────────╮
│ --install-completion          Install completion  │
│                               for the current     │
│                               shell.              │
│ --show-completion             Show completion for │
│                               the current shell,  │
│                               to copy it or       │
│                               customize the       │
│                               installation.       │
│ --help                        Show this message   │
│                               and exit.           │
╰───────────────────────────────────────────────────╯
╭─ Commands ────────────────────────────────────────╮
│ goodbye                                           │
│ hello                                             │
╰───────────────────────────────────────────────────╯

Directly create an spec AST in the target language

Instead of parsing an intermediate JSON file.

Test functionality with term-transcript

https://github.com/slowli/term-transcript

Option to make `=` in CLI options mandatory

Add boolean option to spec to set that CLI options must always use a = (e.g. --option=value instead of --option value).
Should probably be activated by default?

Use `include_dir` for including source files

https://docs.rs/include_dir

Generate a simple GUI app from spec

Completions

Support for user provided config file

Would be stored at ~/.config/my-app/config.ncl

Support for env variables

Loads env variables for flags and options which are not specified.
(e.g. TOOL_OPTION=value would be the same as --option=value)

Support external subcommands

Like they are supported by git:

$ cat /usr/local/bin/git-grin
#! /usr/bin/env bash
echo '😁'

$ git grin
😁

Add command to automatically write the documentation into a markdown file

E.g. have a special comment like:

<!-- Oclis CLI Documentation Start -->
…
<!-- Oclis CLI Documentation End -->

that gets replaced when executing:

oclis insert-docs readme.md

Add subcommand `oclis init`

Creates a specification file skeleton at oclis.ncl.

airsequel / oclis Goto Github PK

oclis's People

Contributors

Stargazers

Watchers

oclis's Issues

Add an ANSI art option a la Python's Typer

Directly create an spec AST in the target language

Test functionality with term-transcript

Option to make `=` in CLI options mandatory

Use `include_dir` for including source files

Generate a simple GUI app from spec

Completions

Support for user provided config file

Support for env variables

Support external subcommands

Add command to automatically write the documentation into a markdown file

Add subcommand `oclis init`

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent