Deserializing yaml structure with enumeration fails about figment HOT 5 CLOSED

That functionality is now available in the just release 0.10.14.

from figment.

That's awesome, thanks for the quick turnaround. Just verified that 0.10.14 works with my use case. I really appreciate it!

From the serde_yaml documentation I thought the "bang-tagging" syntax was the way to go. I like the default serialization representation better.

from figment.

Hmm, looking at the dependencies I used I now realize that I'm mixing different versions of serde and serde_yaml. I used the same version of serde_yaml as Figment to make a fair test, but pasted the serde version for deserialize trait from my app. Could this be the root cause of my issues perhaps?

Edit: Never mind, I just saw that serde_yaml hasn't reached 1.0 yet.

from figment.

Interesting. The YAML crate has a special encoding for custom data type tags, i.e. !Foo, that it recognizes. For instance, that YAML doesn't deserialize into a serde_json::Value either:

let conf: serde_json::Value = serde_yaml::from_str(YAML).unwrap();

// called `Result::unwrap()` on an `Err` value: Error("scripts[0].trigger: invalid type: enum, expected any valid JSON value", line: 4, column: 14)

Perhaps we can emulate the behavior.

from figment.

Note that this YAML syntax, which matches the default deserialization representation expected by Rust enums generated by #[derive(Deserialize), works just fine:

scripts:
  - path: pong.script
    trigger:
      Start:
  - path: ping.script
    trigger:
      Inter:
        sec: 5

from figment.