Closed flaviostutz closed 1 year ago
I ran into this issue while writing unit tests as well! Loading a configuration in a folder/path that doesn't exist throws that.
Shall we just suppress the error and use default configurations instead? Or throw a "missing configuration file" error?
I can pick this one up! :)
closed by #39
It seems this is due to not using default configuration, which is a bug