Error marker appears on first child instead of parent

[tedepstein]

This Swagger spec includes an error on line 54, introduced by removing the leading slash from the /pets/{petId} path. The problem reported is object has properties "pets/{petId}" which are not allowed.

Within the limitations of the current validation, we would expect this error to appear on the paths property on line 7, which is the parent object having the invalid property. However, it appears on line 8, which is the first child of paths (and first sibling of the offending property).

[tedepstein]

Likely the same issue observed in #54.

I think our understanding and expectation of the current logic was incorrect. SwagEdit doesn't place the marker on the "parent". The Swagger object described in #54 is top-level, and therefore has has no parent. And the parent of the Path Item Object described in this issue is the Paths Object. "Paths" is a key, or property name; and the Paths Object is the property value.

So there is consistent logic here: SwagEdit puts the error marker on the first line of the invalid object. Again, it's not "wrong" per se, it's just not intuitive.

We could address this issue with slightly more intuitive logic: If the subject of a validation error is an object; and the object is the entire value of a containing property (i.e. the object is not an array element, and is not the top-level Swagger object) place the error marker on the property name declaration.

We could improve this further by placing property-specific error markers on the property declaration line, as described in #95.