Issue:
Users would like the option to specify configuration settings for the tool via a TOML file located in their home directory. This would allow them to store default options in a configuration file rather than passing them as command-line arguments every time.
Proposed Solution:
I propose adding support for a TOML configuration file in the user’s home directory (e.g., ~/.github-echo-config.toml). The tool would read and apply configuration settings from this file, with the ability to override them via command-line arguments.
Details:
The tool should look for a .toml file in the home directory.
If the config file is missing, it should be ignored.
If the config file is present but cannot be parsed, the tool should exit with an appropriate error message.
Any settings specified in the config file should be used unless overridden by command-line arguments.
The tool should ignore any options in the config file that it doesn’t recognize.
Example Config File:
model = "gpt-4o"
api_key = "sk-..."
TOML Parsing Library:
There are several well-maintained TOML libraries available. I will research and select one that best fits the project’s existing codebase.
Issue:
Users would like the option to specify configuration settings for the tool via a TOML file located in their home directory. This would allow them to store default options in a configuration file rather than passing them as command-line arguments every time.
Proposed Solution:
I propose adding support for a TOML configuration file in the user’s home directory (e.g.,
~/.github-echo-config.toml). The tool would read and apply configuration settings from this file, with the ability to override them via command-line arguments.Details:
.tomlfile in the home directory.Example Config File:
TOML Parsing Library:
There are several well-maintained TOML libraries available. I will research and select one that best fits the project’s existing codebase.