Module config 

Where qcli keeps its settings: cli.conf in the Quvyta ecosystem’s folder, beside the other Quvyta apps.

~/.config/quvyta/
    quvyta.conf     the language, theme and icons every Quvyta app shares
    cli.conf        qcli's settings: the provider it talks to

The provider is four keys: the address, the model, the file the key is in and the header the key goes in. The key itself is never in this file, which people copy between machines and paste into reports; only the path of the file that holds it.

Structs

Provider

The provider as the settings describe it. Every field is what the person wrote, trimmed.

UpdateFolders

Where the ecosystem’s update notice reads its switch and remembers when it last asked.

Enums

Missing

Why the provider cannot be asked yet.

Constants

ADDRESS

The key of the address the Messages API lives under.

APP

The application’s id in the ecosystem: its settings file is cli.conf.

DEFAULT_HEADER

The header most servers of the Messages shape read the key from.

KEY_FILE

The key of the path of the file the key is read from.

KEY_HEADER

The key of the header the key goes in.

MODEL

The key of the model asked for.

Functions

load

The settings from the ecosystem’s folder, checked and healed.

load_in

load from folder as the ecosystem’s folder, so a test never touches the person’s own settings.

preferences

The language, theme and icons as qcli sees them: its own when its file names one, else the ecosystem’s, else what this machine asks for.

schema

What qcli’s own keys may hold. Every value is text; an empty one is the same as none.

spoken

The languages qcli speaks, for choosing the machine’s one before the runtime is built.