This is an experiment in configuration management. The approach is not to create a "parsable" config file format. We have plenty of those. Instead we try to specify a grammar for describing configuration values that can then target various configuration formats to output to.
In theory this could support anything from command line flags to json to yaml or toml or even xml.
The goal is to allow a global shared configuration repository that can be version controlled, enforce some typesafety, and output configuration for any application regardless of that applications preferred format.
This is still very much an experiment and the language and api can be expected to change and mutate. It also probably has bugs and isn't yet the most user friendly language and compiler to use. You have been warned.
You can get ucg with cargo cargo install ucg.
Running ucg help will show the following output.
```sh Universal Configuration Grammar compiler.
USAGE: ucg [SUBCOMMAND]
FLAGS: -h, --help Prints help information -V, --version Prints version information
SUBCOMMANDS: build Build a specific ucg file. help Prints this message or the help of the given subcommand(s) inspect Inspect a specific symbol in a ucg file. validate Check a specific ucg file for errors. ```
```sh Build a list of ucg files.
USAGE: ucg build [FLAGS] -r [INPUT]...
FLAGS: -h, --help Prints help information -r Whether we should recurse in directories or not. -V, --version Prints version information
ARGS: ... Input ucg files or directories to build. If not provided then build the contents of the current directory. ```
```sh Check a list of ucg files for errors and run assertions.
USAGE: ucg validate [FLAGS] -r [INPUT]...
FLAGS: -h, --help Prints help information -r Whether we should recurse or not. -V, --version Prints version information
ARGS: ... Input ucg files or directories to validate. If not provided scan the directory for files with _test.ucg ```
https://docs.rs/ucg/