@axway/api-builder-oas-flow-node

@axway/api-builder-oas-flow-node

Changes

2.5.1

• #7139: Normalise the case of response content media-types and headers in internal OpenAPI representation.

2.5.0

• #7284: Now preserves the OAS 2 body name in op.requestBodyName.

2.4.0

• #7303: Added option to disable stripping formats from JSON schema.

2.3.0

• #7282: The exported schemas now have their draft version set in $schema property.

2.2.1

• #7111: Internal refactoring.

2.2.0

• #7155: Fixed issue with CVE-2021-3918 and removed the dependency on the request library.
• #7155: Fixed an issue where the 'Authorization' header could not be unset (i.e. it was set to null in the Advanced HTTP Options).

2.1.1

• #7123: Changed json-pointer dependency to @axway/json-pointer as a fix for CVE-2021-23820.

2.1.0

• #7132: Added additional parameter properties for style and explode options.

2.0.4

• #7105: Response body is no longer logged at DEBUG to improve performance.

2.0.3

• #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".

2.0.2

• #7057: Updated documentation links.

2.0.1

• #6295: Ensured Server URL parameter of generated Flow-node(s) is editable.

2.0.0

• #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).
• #5352: Added support for OAuth2 Client Credentials.

1.2.6

• #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' }.

1.2.5

• #6934: Internal refactoring around code style.

1.2.4

• #6938: Updated @axway/axsway to resolve security issue with z-schema.

1.2.3

• #6783: Internal refactoring.

1.2.2

• #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.

1.2.1

• #6546: Update ajv dependency.

1.2.0

• #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.

1.1.0

• #6549: Fix regression where basePath could not be overridden in config for OAS2 definitions.
• #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.
• #6412: Added custom HTTP headers to generated flow-nodes using @axway/api-builder-plugin-fn-swagger.

1.0.4

• #6412: Upgrade to @axway/api-builder-sdk@1.0.0.

1.0.3

• #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.

1.0.2

• #6320: Fixed Uncaught Exception Unable to register flow-node on API Builder startup when handling OAS2 definitions with response schemas that were type: "file".

1.0.1

• #6318: Fixes unused references warning.
• #6315: Internal chore.

1.0.0

• #6277: Initial release