You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be useful to enable codebase for extensions e.g., to be able to provide own ajv validator or an instance of determiner.
To my understanding determiner logic is responsible for augmenting the source schema and example extraction.
Thus having the ability to provision augmentation logic and / or ajv instance could help to realize some more complex jet bespoke use cases like: handling noAdditional properties for complex schemas (using unevaluated Properties), support for readOnly/writeOnly etc.
The text was updated successfully, but these errors were encountered:
bartoszm
added a commit
to bartoszm/openapi-examples-validator
that referenced
this issue
Sep 27, 2023
The validator-factory is to initialise the JSONSchema-Validator (which then will be used to validate the OpenAPI-definitions). It can be used to augment the OpenAPI-definition. However, it was never intended to make extensive adaptions/augmentations as the main task of the validation should be done by the JSONSchema-validator (Ajv, in this case). Any modification of the original OpenAPI-definition, just to handle or cover shortcomings of the JSONSchema-validator, may lead to unwanted or unforeseen side-effects and in the worst case may lead to wrong validation-results. That is why I try to keep it at an absolute minimum.
I think it would be useful to enable codebase for extensions e.g., to be able to provide own ajv validator or an instance of determiner.
To my understanding determiner logic is responsible for augmenting the source schema and example extraction.
Thus having the ability to provision augmentation logic and / or ajv instance could help to realize some more complex jet bespoke use cases like: handling noAdditional properties for complex schemas (using unevaluated Properties), support for readOnly/writeOnly etc.
The text was updated successfully, but these errors were encountered: