forked from loafle/openapi-generator-original
88efb28506
This adds some conistency to how validation properties are persisted to the Codegen* types. Whenever we extract metadata from an OpenAPI Schema, that metadata may include properties defined in the JSON Schema Validation specification section 6 (see https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.6). Previously, only some of these were copied. This creates an interface allowing for consistent type access across: * CodegenModel * CodegenParameter * CodegenProperty * CodegenResponse This does _not_ change existing public fields which previously exposed these on some of the above type (see CodegenParameter). CodegenModel has a legacy edge case where primitive types could be represented at that level rather than as a referenced schema. This adds the sync of validation properties to these primitive constructs for CodegenModel with a note that they're legacy and likely to be removed later.