Pascal

Requires https://github.com/eclipse-vertx/vertx-openapi/pull/28

> Thank you @pk-work > > Have you been able to get to the bottom of the failures? Not yet, @pmlopes maybe you have an idea why the tests with...

Hi, with Vert.x 4.4 we released a complete re-build of Vert.x OpenAPI [1]. Especially the error messages which are now generated are very helpful. They now look like this: `The...

For now I'm not convinced that a `getParameterName()` is beneficial in general, because if the "path" contains cycles the name of the property isn't enough to identify the error location....

A function that returns the JSON Path / Pointer to the problematic property would make sense in my opinion,, but not only the "name".

Hi @InfoSec812 @javadevmtl @pantinor @Fyro-Ing @tsegismont , as I mentioned above, it is not that easy to identify the "parameter" which causes the issue, at least not if you want...

> How does it work on vertx-3? I don't know exactly. But this what the new JSON Schema validation engine provides. Maybe it was possible, because the old engine wasn't...

It will return the keywordLocation like `#/items/$ref/oneOf/2/$ref/allOf/1/properties/modelType/pattern`

It will return the "keywordLocation" of the first error from OutputUnit. If there is only one error, it will work, otherwise you need to call getCause() recursively. Here [1] is...

After some discussion, we believe that the best solution is to make the errors from the OutputUnit easily consumable. Then everyone can parse the necessary information from the errors.