00JCIV00

Generate Command Tree in an easily parsable format.

10

Per talks with @matu3ba: - The list should be easily parsable for all shell languages for selection by the user as shell script (for now) with listing most relevant items...

A new function, `cova.genCompletions()`, should generate completions for provided argument tokens based on a Command. Very similar to `cova.parseArgs()`. This can be used to generate completions in custom CLIs or...

Every public function in the library should be tested either individually or in a group similar to how the tests in `src/cova` work. Additionally this testing should be conducted across...

Review the use of `const` and `@constCast` throughout the library

1

The use of `@constCast` is generally discouraged, but it's used throughout the library in the Command, Option, and Value types. There two main reasons for this: 1. A desire to...

If possible, Argument Type metadata should be optionally pulled via AST Parsing of type/field comments.

Mimic the Diagnostic pattern from [`std.json.Diagnostics`](https://ziglang.org/documentation/master/std/#std.json.scanner.Diagnostics) to provide better error handling to library users. This should be provided as an Optional Struct via the `cova.ParseConfig`.

Introduce a new function for Commands called `fromHelpMessage()` (or similar) that allows users to create Commands from a string that's setup like a Help Message. If possible, this Help Message...

Currently, the UsageHelpConfig works under the assumption that library users will always want to either use both Usage and Help or neither, but not one or the other. It's also...

- Heap allocated `vxfw.App` to prevent invalid stack pointer. - Implemented Saturated Operators (`-|`, `+|`, `*|`) where able in `vxfw.zig`. This forces the various `assert`s to actually be reachable. -...