Allow application.conf to be located anywhere on the classpath

Currently it appears that ScalaSMT opens its configuration file application.conf in the current working directory of the process. This causes problems for the LSP version of Skink since, ideally, we should let the user specify which application.conf they want to use. Currently things only work if the current working directory of Skink process is a directory that contains the application.conf.

Can you add a way to customise this? The option that seems easiest is to look for the configuration file on the classpath of the process, since the editor extension can easily add to a user-specified location to the class path before it runs Skink. The Typesafe Config docs say that it "can load from files, URLs, or classpath", so hopefully this is not too hard to do.

Comments (3)