Repeated revalidate() raises Invalid state

[kputyra]

Repeated revalidate() raises Invalid state

[aschankler]

It looks like adding default keys scrambles the order of the state of the YAMLChunk object, leading to inconsistency between the ruamel parsing and the strictyaml parsing. This is the same outcome as in #184, where a failed revalidation leads to inconsistency. In the original example:

from strictyaml import load, Map, Int, Optional

doc = "x: 1"
schema = Map({ "x": Int(), Optional("y", default=42): Int() })
yml = load(doc, schema)

yml._chunk.strictparsed()
# ordereddict([(YAML(x), YAML(1)), (YAML(y), YAML(42))])
yml._chunk.contents
# ordereddict([('x', '1')])

yml.revalidate(schema)
yml._chunk.strictparsed()
# ordereddict([(YAML(y), YAML(42)), (YAML(x), YAML(1))])
yml._chunk.contents
# ordereddict([('x', '1')])

The mismatch between these two internal states causes trouble when resolving keys in YAMLChunk.expect_mapping called by Map.validate.

[callegar]

I am also experiencing the issue.

Guess it can be worked around by non revalidating... but...

Otherwise, I wonder if dealing with optional stuff by using a MapCombined and to then explicitly look for some keys and add them with the default values if missing would cause the same issue.

But in fact, would be glad to know if a fix is possible or far away in a pipeline of more urgent stuff...