Closed Rhiannon-Udall closed 1 year ago
I am not sure what would be different between the first case and the second besides the depth.
Compare this part:
"r":{
"properties":{"mergeStrategy":"append"}
}
with this part:
"h": {
"mergeStrategy":"append"
}
Hello,
I found this package today, and it seems like it should do exactly I want for a thorny input parsing problem. However, I found behavior which seems pathological at increased depth into the json. In particular:
yields
In particular, one may note that the append strategy seems to work correctly at one level of depth (g/h) but fails at another (n/p/r). Perhaps this is a subtlety of setting up the merge schema, though I am not sure what would be different between the first case and the second besides the depth.