Schema validation with dynamic keys about karate HOT 3 CLOSED

not sure if this is simple tbh. personally I consider the need to validate keys rare and due to badly designed APIs. also am more worried about issues like this: #2515 - because that is core to karate

the last line is honestly a bit hard to read and understand. so I'm concerned about that. you are welcome to try a PR

from karate.

Thanks @ptrthomas

Agreed about the last line being a bit hard to read.
For consistency with the other fuzzy markers, maybe declaring #dict as a property, not a key, would make more sense.
Something like:

{ data: #dict({
    name: #string,
    airports: #dict({
      name: #string
   }
}

Not sure it would be more understandable, though. And definitely very complicated to implement.

The other interesting thing in your comment is issue #2515. There's a risk, albeit small IMO, that this new marker would introduce a similar regression. Also, how would it integrate with contains [only [deep]]? Something to thing about ...

Anyway, I'm hoping to raise a PR for feedback in the coming days, with the initial suggestion.

from karate.

(on hold while looking at #2515 and learning more about shortcuts and whether they could help here. It seems that every month i learn a new amazing feature in Karate!)

from karate.