Add functionality for validating data against models about prance HOT 3 OPEN

• JSON schema validation for Schema Objects
• extended validation of Schema Objects according to specs
• Evaluate/implement validation of Header Objects.
• Evaluate/implement validation of Response Objects.
• Evaluate/implement validation of Parameter Objects.
• Evaluate/implement validation of Example Objects.
• Evaluate/implement validation of Request Body Objects.
• Evaluate/implement validation of Security Scheme Objects.
• Evaluate/implement validation of Link Objects.
• Evaluate/implement validation of Callback Objects.
• CLI command

from prance.

@jfinkhaeuser that one is most interesting, i presume it was stalled for personal reasons?

from prance.

Yes - I think the PR can be closed, unfortunately.

When I started the whole project, it was born out of a desire to run automated API tests. E.g. connexxion validates input data lazily, and doesn't validate output data (as far as I recall from back then).

I much prefer contract-based development, where inputs and outputs are validated at API boundaries (outputs in production less so, but in development/CI).

I felt the first step here was to implement the functionality for validating data against specs in a standalone tool that can also be used as a library. Then you can re-use the library as needed.

As a side note, the specs allow for example sections. It would have been a next step to extract examples, and check that they actually validate as well. This is, of course, optional because examples do not have to have any specific format. But it would allow using examples for bundling test data with the specs themselves.

from prance.