Feature request: an option to disable config warning when running via the REPL

[weavejester]

When running kaocha.repl/run-all, we can specify a configuration that will override the default configuration found in the test.edn file. In theory, this means that the entire configuration could be specified this way... except that Kaocha will raise a warning if test.edn is missing, even if it given a complete configuration via an argument.

For example:

(kaocha.repl/run (kaocha.config/default-config))

Produces:

WARNING: Did not load a configuration file and using the defaults.
This is fine for experimenting, but for long-term use, we recommend creating a configuration file to avoid changes in behavior between releases.
To create a configuration file using the current defaults and configuration file location, create a file named tests.edn that contains '#kaocha/v1 {}'.

My suggestion would be to allow an option like :kaocha/disable-missing-config-file-warning? that, when set to true, suppresses the warning message. This would ensure that people don't accidentally disable the warning, but can do so if they really want to.

If this is okay, I can submit a pull request that implements this change.

[weavejester]

Alternatively, I could go through kaocha.api if that's intended to be used instead in more advanced REPL configurations, but it seems like I'd duplicate a lot of the kaocha.repl namespace with that approach.

[weavejester]

I've looked into this a little further and found that I need to fall back on kaocha.api for a couple of other things, so I think for my particular use case it's worth me going the whole way and just using the API. As I no longer have a use case for this issue, I'll close it.

(As an aside, Kaocha's codebase has so far been very well laid out. I've seen quite a lot of tools that aren't designed to be used outside the command line, and it shows in their codebase. But Kaocha seems so far to be very usable as a library as well, so full marks for that.)

[plexus]

We'll leave this as is then. If someone else comes across this issue with a similar problem, I do agree that when calling kaocha.repl/run with a config map the warning doesn't make much sense. I'd be ok with the proposed solution of an extra flag to hide the warning, I'd also be ok with simply not showing it by default when using that pathway.

Kaocha's codebase has so far been very well laid out

Thanks a lot for the compliment 😄 I tried to make it very data driven, I'm glad that it shows.