-
Notifications
You must be signed in to change notification settings - Fork 6
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
Can't use raw Vec for config #39
Comments
Hello Honestly, it seems unusual and it never crossed my mind to try that, so I'm not very surprised it doesn't work. But if you feel like wanting to provide a fix, I'm totally fine with accepting it. Two things I'd suggest you try: What happens if you wrap it in a structure like this?
I suspect the real issue is in the |
I’ll have a play!
It makes sense for me as I’m ingesting a bunch of metric definitions (and
nothing else)
Thanks for the quick response!
…On Fri, 31 May 2019 at 6:06 pm, vorner ***@***.***> wrote:
Hello
Honestly, it seems unusual and it never crossed my mind to try that, so
I'm not very surprised it doesn't work. But if you feel like wanting to
provide a fix, I'm totally fine with accepting it.
Two things I'd suggest you try:
What happens if you wrap it in a structure like this?
struct Config {
#[serde(flatten)]
string: Vec<String>,
}
I suspect the real issue is in the config crate, can you try directly
with that (spirit adds all that fancy reloading on SIGHUP and combining
with command line, but the parsing is done by that crate).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#39?email_source=notifications&email_token=AAJJDIZHMM3EUE45WIG7SRDPYDL7XA5CNFSM4HRVJH62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWUQVVY#issuecomment-497617623>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJJDI4M3J5NZO52MMC7K6DPYDL7XANCNFSM4HRVJH6Q>
.
|
Hi,
I want to use
Vec<MetricGroups>
as my config file format - but it doesn't seem to work.Is this a supported feature?
When I use a
Vec<String>
I get the same issue, but if I wrap it in a struct like so:Then I have no issue.
The text was updated successfully, but these errors were encountered: