Currently, we use the global logger to log errors and other information during calls to medusa init and medusa fuzz. However, the problem with this is that we are unable to validate the LoggingConfig config options until NewFuzzer is called. For example, you can set NoColor to true but the global logger will still output color. Personally, the best thing to do is not use a logger in the cmd package and stick with fmt.Printf statements. I think this is generally a well-founded practice.
The other option is to validate the logging config before NewFuzzer however this causes some complications:
You won't be able to do it for the init command since a config is not provided.
Currently, we use the global logger to log errors and other information during calls to
medusa initandmedusa fuzz. However, the problem with this is that we are unable to validate theLoggingConfigconfig options untilNewFuzzeris called. For example, you can setNoColortotruebut the global logger will still output color. Personally, the best thing to do is not use a logger in thecmdpackage and stick with fmt.Printf statements. I think this is generally a well-founded practice.The other option is to validate the logging config before
NewFuzzerhowever this causes some complications:initcommand since a config is not provided.