v2.0.0
What's Changed
-
Configuration has moved! TOML is now used in place of the YAML user configuration file. It also now lives within the package itself instead of user home configuration directories (xdg_config, etc).
-
More CLI subcommands exist for configration management. `proxima config [edit|view|reset] [toml|dotenv|env]. Dotenv makes for easier development configuration. Environment variables are directly supported. Toml is populated by default and easily resettable, similar to old YAML settings.
-
Pydantic is used for settings static/dynamic typing as well as runtime validation
-
Prompting subsititution for missing or invalid keys is no longer supported. It was overly complex, slow and glitchy. Especially when entire configuration sections were absent, since a user couldn't be expected to enter ALL the missing settings in a single prompt at runtime.
Why
- Increase startup speed
- Decrease circular import issues,
- TOML > YAML (stricter types),
- Pydantic is more maintainable/optimised
PRs
- refactor: SettingsManager with TOML and better practices by @github-actions in #258
Notes:
I'm a noob and my feat
and BREAKING CHANGE
message was disregarded by the Semantic Release action. I thought it parsed the commits, not the PR title...
Full Changelog: v1.0.5...v2.0.0