When adding new features, it is often the case that the config struct is extended. Since the struct was previously generated via the config file, which is maintained by the user, it would require them to actively add the missing entries in their configs.
For instance, the new timestamp formats are stored in the config. A user without those entries in their config will see something like:
-- Replying to [username] @ --
instead of the expected
-- Replying to [username] @ 10:45 --
With a default configuration built into the application:
the user can keep their current config file (even though some entries might be the same as the default settings)
new features do not require the user to add those entries to the config
by default, no actual config file is required - making the effort of maintaining a config file optional if the user has no special config
Hi!
When adding new features, it is often the case that the config struct is extended. Since the struct was previously generated via the config file, which is maintained by the user, it would require them to actively add the missing entries in their configs.
For instance, the new timestamp formats are stored in the config. A user without those entries in their config will see something like:
-- Replying to [username] @ --
instead of the expected
-- Replying to [username] @ 10:45 --
With a default configuration built into the application:
Cheers!