#7538: Fixed an issue where the request content-length header was calculated incorrectly when the request body was a string that contains multi-byte characters.
#7538: Fixed an issue where the request content-length header was calculated incorrectly when the request body was a string that contains multi-byte characters.
#7059: Fixed an issue loading OAS spec with the error "Cannot convert undefined or null to object". The issue was encountered on OAS specs containing mixed references to component properties, e.g. "#/components/schemas/Pet/properties/name" and references to components, e.g. ""#/components/schemas/Pet".
#7010: Internal refactoring around testing input / output validation.
#7010: OAS methods that describe binary input { type: 'string', format: 'binary' } will now generate parameter schema of type any (i.e. {}) instead of { type: 'string' }.
#6732: When an instance of APIBuilder is not found, (which can occur when testing from a sub-directory of an API Builder project), a config will not be generated for the OAS plugin. Instead of throwing no @axway/api-builder-runtime instance, it will now just emit a warning.
#6732: Updated OAS validation to include any error detail in the thrown error instead of logging the details separately.
#6296: Added optional Advanced HTTP Options Headers parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.
#6322: Previously, references to schema definitions/components that had keys containing URI reserved characters (RFC-3986 section 2.2) (e.g. "Pet!") would be incorrectly encoded, causing a runtime error, "MissingRefError: can't resolve reference schema:///...". Now, references are correctly encoded.
#6320: Fixed Uncaught Exception Unable to register flow-node on API Builder startup when handling OAS2 definitions with response schemas that were type: "file".