- Leverage ajv /asyc in serdes deserialization.
- Leverage passContext for format.validate, deserialize, serialize
- Add tests for async and context
- Allow HttpErrors thrown from deserialize to influence errors thrown to express error handling pipeline.
- Modify schema pre-processor to not share memory between ajv instance and apiDoc.
- Modify schema pre-processor to not share memory between request and response apiDoc.

…ture.

…re test coverage for async-utils.

…rows HttpErrors. Deviates when deserialization is occuring in query/body/params. Functionality is a no-op if package consumers throw an Ajv.ValidationError from their deserialize function instead of an HttpError.

…o didn't have tests.

…chema. Make sure the schema passsed to compile has if it needs it. Additionally add test coverage, and make sure the ajv instance used for preprocessing respects passContext config for validateRequests.

…el schema has a dscriminator would lose the /body prefix of the instancePath, making error messages inconsistent. Additionally, respect the actual class type of an HttpError thrown from a deserialize/validate function.

…he provided discriminator property value.

… sub-schemas.

…e request if those properties are not set in data.

…so it shows up in errorCode.