If rule PatchBodyParameterSchema fails, the error message only includes the name of the property and the top-level reference that contains the nested property:
This can be very difficult to debug, especially if the property is nested multiple levels or is under common-types which spec authors asssume are 100% correct.
Can the rule be improved to show the original source location of the violation? Or a "call stack" of $refs?
I'm unsure if this behavior is specific to PatchBodyParameterSchema, or applies to many (or all) rules.
If rule
PatchBodyParameterSchema
fails, the error message only includes the name of the property and the top-level reference that contains the nested property:This can be very difficult to debug, especially if the property is nested multiple levels or is under
common-types
which spec authors asssume are 100% correct.Can the rule be improved to show the original source location of the violation? Or a "call stack" of $refs?
I'm unsure if this behavior is specific to
PatchBodyParameterSchema
, or applies to many (or all) rules.