that's a good question, and the docs needs a bette...
# core
t
that's a good question, and the docs needs a better interface to specify this expectation of how a flag can be set and used. Like you can absolutely set a flag in the options, say the
config_plugin
like you mentioned, but how do you know if it'll do anything? Aka where is the flag used? The
--help
breaks flags into two categories, those that should only be set at startups/CLI, and those that can be set in the options. The docs misses this differentiation, furthermore, there's nothing enforcing/testing this labeling. I am free to label a flag as CLI + options and then only use it once when the program is starting up, before the config is read 😛