Make the AdditionalPropertiesInjectionTransformer Optional
Issue #369
new
As the FAQs says, the reason behind the injection of additionalProperties: false in the schema is arbitray and a utility for testing mocks, but this alters the semantics of validation raising errors where it shouldn’t and also leading to validation bugs with allOf.
We are currently forking the library exposing the list of transformers and then removing the AdditionalPropertiesInjectionTransformer, can the list of transformers be configurable for the given SchemaValidator?