-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose coalesce module #74
Comments
Which things would be helpful? And how do you plan to use them? |
Right now, I'm just copying the whole for (k, v) in self.data.iter().map(|(k, v)| {
let key = k.to_ascii_lowercase().replace('_', ".");
(key, v.to_owned())
}) {
let nested_dict: std::collections::BTreeMap<String, figment::value::Value> =
nest(k.as_str(), v.parse().expect("infallible"))
.into_dict()
.expect("key is non-empty: must have dict");
dict = dict.merge(nested_dict);
}
let profile = Profile::default();
Ok(profile.collect(dict)) |
I do eventually want to expose the implementations underling the module in some form, but I'm not sure exposing it directly is the right way. I'll give this some more thought and post an update later day. |
The
figment::coalesce::Coalescible
trait seems very helpful when writing providers, any chance to make thatpub
?The text was updated successfully, but these errors were encountered: