Lukas Kalbertodt
Lukas Kalbertodt
Hi. I'm sorry but I think you need to provide a bit more context. What do you mean by "modification of config files"?
Ah I see. That makes sense. This is something I very likely will consider for `confique`. In fact I might have this exact requirement very soon in one of my...
Yep :/ I am very sure that `confique` will stay with serde and not pull in any other dependencies.
Fair point. It's certainly worth considering how one could support multiple cli libraries. Or even be completely library-agnostic.
And I assume you can't simply annotate your struct with `#[allow(clippy::missing_docs_in_private_items)]`? So this crate would have to add said attribute to some items. Now I wonder: - Is it ok...
I will, but I'm currently short on time. Thank you for the PR though. I'll try to get to it sometime soon, but no promises.
The problem is that confique deserialization from environment variables only works for basic types, but not lists or maps (also see #10). So I don't think `.env` is a format...
The `template` functions cannot emit compile errors as they are simple functions running at runtime. And the `Config` derive macro doesn't know whether you just want to load it from...
> If the `list_by_*` function is used, then add a message about it to template. We can't know that. Right now, `meta` types do not contain information about `parse_env`. But...
@amkartashov could you describe your use case in more detail? Maybe some example code how you wish `confique` would work?