Config File Restrictions

[jolhoeft]

For my application, I need a small amount of config information. Not wanting to have multiple config files, I just added a field to my 0.5.x Log4rs config file containing my config information, which worked fine. I just upgraded to 0.7.x, and Log4rs can no longer parse the config file. This problem appears to be Serde deserializing into Log4rs' RawConfig struct, seeing an unexpected field (my config data), and returning an error. I'm using the toml format.

Do I have any options except splitting this into two config files?

[sfackler]

I should work just fine embedded in a larger config structure:

#[derive(Deserialize)]
pub struct Config {
   pub logging: log4rs::file::RawConfig,
   pub other_thing: u32
}