NAME

App::Moneymoor::Config - the data home, the budget file list, and the four global display settings.

SYNOPSIS

use App::Moneymoor::Config;

my $cfg = App::Moneymoor::Config.new;
$cfg.load;                          # reads ~/.moneymoor/config.json

say $cfg.available-budget-names;    # ('household', 'business')

$cfg.budget-name = 'household';
say $cfg.budget-path;               # /Users/you/.moneymoor/household.db

$cfg.theme        = 'nord';
$cfg.icons        = 'nerd';
$cfg.currency     = '€';
$cfg.decimal-mark = ',';
$cfg.save;                          # back to ~/.moneymoor/config.json

DESCRIPTION

Moneymoor keeps everything under one directory:

~/.moneymoor/
      config.json          # this file: last-used budget, theme,
                           #            icons, currency, decimal mark
      household.db         # a sqlcipher budget
      business.db          # another one
      logs/error.log       # Selkie's stderr redirect while the TUI runs

Budgets are flat files in the data home, not per-profile subdirectories: a budget is a single sqlcipher database with no sidecar state, so a directory per budget would be a directory containing exactly one file. The login screen lists ~/.moneymoor/*.db and the basename is the budget name.

Everything is derived from moneymoor-home, which honours the MONEYMOOR_HOME environment variable. That override exists for the test suite — a test that wrote to the real ~/.moneymoor could clobber a user's budget list — but it is equally useful for keeping a throwaway budget out of the normal picker.

What is not here

Nothing about a budget's contents. Category order, hidden flags, collapsed groups and the viewed period all live in the encrypted database or in the Selkie store, because they are per-budget facts and this file is deliberately plaintext (it has to be readable before a passphrase exists — the login screen is themed from the first frame).

ATTRIBUTES

• budget-name — the last budget opened, pre-selected by the login screen next launch. Defaults to 'budget'.

• theme — palette name, resolved through App::Moneymoor::Themes::load. Defaults to 'gruvbox'.

• icons — glyph tier, 'unicode' (default) or 'nerd'. Resolved through App::Moneymoor::Service::Icons::icons, which maps an unknown tier back onto unicode, so a hand-edited config cannot break rendering.

• currency — the symbol money is rendered with: '£' (default), '$' or '€'. Display only — App::Moneymoor::Util::Money converts nothing and the engine has never heard of a currency.

• decimal-mark — '.' (default) or ',', stored under the JSON key decimal_mark. Thousands are grouped with the other one, so this single setting moves both characters, in both directions: '1,234.56' or '1.234,56' on the way out, and the matching shape accepted on the way in.

currency and decimal-mark are the two settings this class validates, because they are the two that are handed to a routine that refuses an unknown value (set-money-locale throws). A value outside the whitelist — a hand-edited "currency": "CAD" — falls back to the default silently, the same treatment Service::Icons gives an unknown glyph tier: the plaintext config is user-editable by design, and the failure mode for a typo in it must be "the app opens in £" rather than "the app does not open".

METHODS

• moneymoor-home — ~/.moneymoor, or $MONEYMOOR_HOME.

• budget-path — derived ~/.moneymoor/{budget-name}.db.

• budget-path-for($name) — the same derivation for any name, for the login screen's "open the one the user just picked".

• budget-exists — is there a file at budget-path?

• available-budget-names — every *.db basename in the data home, most-recently-modified first, so the picker opens on the budget the user was last in.

• valid-budget-name($name) — the create-a-budget name rule: letters, digits, ., _, -. Rejects anything that could escape the data home.

• error-log-path — ~/.moneymoor/logs/error.log, handed to Selkie::App so warnings don't splatter over the TUI.

• ensure-directories — create the data home if missing.

• load($path?) / save / config-path — JSON round-trip.

EXAMPLES

Pointing a test at a scratch home

my $scratch = $*TMPDIR.add("moneymoor-test-{$*PID}").Str;
%*ENV<MONEYMOOR_HOME> = $scratch;

my $cfg = App::Moneymoor::Config.new.load;
$cfg.icons = 'nerd';
$cfg.save;

App::Moneymoor::Config.new.load.icons;      # 'nerd'

Opening whatever the user picked in the login Select

my $path = $cfg.budget-path-for($login.selected-budget);
my $db   = App::Moneymoor::DB.new(db-path => $path);
my $res  = $db.connect($passphrase);
if $res ~~ Failure {
    $login.set-status($res.exception.message, :error);
    $res.so;                       # a handled Failure must be defused
}

SEE ALSO

• App::Moneymoor::Screen::Login — the consumer of available-budget-names and budget-path-for.

• App::Moneymoor::Themes — resolves theme.

• App::Moneymoor::Service::Icons — resolves icons.

• App::Moneymoor::Util::Money — owns the whitelists currency and decimal-mark are checked against, and is pointed at them by App::Moneymoor::UI at startup.