I feel as if the solution to this is in front of me using a custom TypeDefinition or something similar but I'm just not seeing it. (I did some customizing of our SnakeYAML parsing some time ago and I'm having to relearn what I have forgotten.)
To process part of the YAML input, I need to translate some input YAML to a `Map<String, MyType>` on the Java object.
Each key in the input YAML can be either an integer or a string.
When SnakeYAML parses those keys that happen to be integers, it understandably creates an integer.
As a result, in `BaseConstructor.constructMapping2ndStep`, the code fails when it tries to `put` the key and value to the mapping because the key type of the map on `MyType` is `String` but the key value SnakeYAML has created is an `Integer`.
What's the cleanest way for me to make sure that, when processing this property on MyType, the key value is created as a `String`?
Thanks.