Introduction

Command for cascading toml "databases" into their full objects

TOML cascades are file trees that define generic configuration. Cascading allows for shared setting to be set in one place.

The root of a cascade has two files that define it:

• .cascade.toml defines settings for cascadetoml. Settings are:
  • paths a list of strings where each string is a python format-style string. These strings are used to pull out setting defined by the path.
• <type>.template.toml defines the full structure of the resulting TOML object. <type> is used as the name for the array of tables output when a cascade results in multiple objects. The keys in the table are the only ones allowed in TOML files within the tree. The types of values must also be consistent.

Settings for a particular folder are in a TOML file with the folder name plus the .toml extension.

The first repo using this is the nvm.toml repo. Its only path is {technology}/{manufacturer}/{sku}.toml. A file such as flash/gigadevice/GD1.toml will have the implicit values:

technology = "flash"
manufacturer = "gigadevice"
sku = "GD1"

All of the other values come from these files in order:

• flash/flash.toml
• flash/gigadevice/gigadevice.toml
• flash/gigadevice/GD1.toml

No key may exist at multiple levels.

cascadetoml check can be used to validate much of this.

Installing from PyPI

To install for current user:

pip3 install cascadetoml

To install system-wide (this may be required in some cases):

sudo pip3 install cascadetoml

To install in a virtual environment in your current project:

mkdir project-name && cd project-name
python3 -m venv .env
source .env/bin/activate
pip3 install cascadetoml

Contributing

Contributions are welcome! Please read our Code of Conduct before contributing to help this project stay welcoming.

Documentation

For information on building library documentation, please check out this guide.