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

api-builder-oas-flow-node

Changes

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 seperately.

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 flownodes 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