23c0b3c547
This would make more sense in user code:
```rs
Yaml::load_from_str("foo"); // Explicit that we're parsing YAML
load_from_str("foo"); // Too implicit, too generic, may be from another
lib
```
Plus, this mirrors `MarkedYaml`'s behavior.
57 lines
1.4 KiB
Rust
57 lines
1.4 KiB
Rust
use saphyr::{Hash, Yaml, YamlEmitter};
|
|
|
|
#[test]
|
|
fn test_mapvec_legal() {
|
|
// Emitting a `map<map<seq<_>>, _>` should result in legal yaml that
|
|
// we can parse.
|
|
|
|
let key = vec![Yaml::Integer(1), Yaml::Integer(2), Yaml::Integer(3)];
|
|
|
|
let mut keyhash = Hash::new();
|
|
keyhash.insert(Yaml::String("key".into()), Yaml::Array(key));
|
|
|
|
let val = vec![Yaml::Integer(4), Yaml::Integer(5), Yaml::Integer(6)];
|
|
|
|
let mut hash = Hash::new();
|
|
hash.insert(Yaml::Hash(keyhash), Yaml::Array(val));
|
|
|
|
let mut out_str = String::new();
|
|
{
|
|
let mut emitter = YamlEmitter::new(&mut out_str);
|
|
emitter.dump(&Yaml::Hash(hash)).unwrap();
|
|
}
|
|
|
|
// At this point, we are tempted to naively render like this:
|
|
//
|
|
// ```yaml
|
|
// ---
|
|
// {key:
|
|
// - 1
|
|
// - 2
|
|
// - 3}:
|
|
// - 4
|
|
// - 5
|
|
// - 6
|
|
// ```
|
|
//
|
|
// However, this doesn't work, because the key sequence [1, 2, 3] is
|
|
// rendered in block mode, which is not legal (as far as I can tell)
|
|
// inside the flow mode of the key. We need to either fully render
|
|
// everything that's in a key in flow mode (which may make for some
|
|
// long lines), or use the explicit map identifier '?':
|
|
//
|
|
// ```yaml
|
|
// ---
|
|
// ?
|
|
// key:
|
|
// - 1
|
|
// - 2
|
|
// - 3
|
|
// :
|
|
// - 4
|
|
// - 5
|
|
// - 6
|
|
// ```
|
|
|
|
Yaml::load_from_str(&out_str).unwrap();
|
|
}
|