API Designer (Pre-Crowd) Release Notes Archive

The mocking service was switched on for the project before January 10, 2019.

The mocking service has been running continuously since it was switched on.

When a uses node referred to a missing file, the error message was not helpful. The error message has been revised.

The API Designer might take so long to validate a RAML API specification and show the API summary that the browser would time out.

The API editor did not throw an exception when an incorrect JSON schema was declared.

A project could be opened without errors in the API editor in Design Center but with errors in API Designer in API Manager.

No error message was displayed when a uses node specified an invalid path to a library.

Importing an API specification written in OAS 2.0 sometimes resulted in the following error: Failed to parse Swagger: Swagger schema validation failed.

Resolved an issue with a warning message path exceeds file system root at (position in file). that should not have appeared for an API specification in the code editor in the following situation: A fragment where the notation ../ is used in a path that references a file that is in a subdirectory of an upper level.

Using facet items in a data type other than Array resulted in an error.

Supplying a base URI parameter in the visual API Designer, using the parameter in a base URI, closing the visual API Designer, and then reopening the project resulted in an error message and a blank middle panel.

Selecting the type Number for a new Data Type in the visual API Designer, specifying a format, and changing the type to Integer resulted in the RAML viewer still including the specified number format.

Changing the type for a base URI parameter caused the RAML viewer to show the new type, but the Type field continued to show the previously selected type.

The OAS-to-RAML converter did not recognize the API Key authentication type. If you tried to import an OAS file that used this type of authentication, the import failed.

Bumped RAML Parser to version to 1.1.29

Bumped API Console to version 3.0.20.

Bumped RAML Parser to version 1.1.26.

Bumped API Console to version 3.0.19.

Fixed an issue with validating the length of a string in RAML data types.

Fixed an issue causing the OAS import to produce the error “Cannot read properly 'hasOwnProperty' of null”.

Bumped RAML Parser to version 1.1.24.

Bumped API Console to version 3.0.18.

Bumped OAS RAML Converter to version 0.2.4.

Export to OAS 2.0: RAML scalar-valued nodes are now mapped into OAS vendor extensions.

Export to OAS 2.0: The value of baseUri is now correctly mapped to its corresponding node in OAS 2.0.

Bumped RAML Parser to version to 1.1.20

Bumped API Console version to 3.0.17

Improved security

Export to OAS 2.0

Fixed an issue with Editor in Chrome that caused the scrollbar bounces up and down when trying to scroll

Show warnings for json schema if it is not compliant with the draft-04 JSON schema

Fixed an issue so OAS is accepted as value instead of SWAGGER when requesting conversions

Bumped RAML Parser to version to 1.1.19

Bumped API Console version to 3.0.16

Fixed the issue with the importer generating invalid facets on RAML types by using annotations instead of custom facets.

Fixed the issue with loading an XSD file when another XSD file was using it.

Fixed the issue with validating additionalProperties.

Fixed the issue with the OAS-RAML Converter converting additionalProperties.

Bumped the JS parser version to 1.1.14.

Bumped the API Console version to 3.0.14.

Added a background process for parsing and validation.

Improved performance by no longer rendering the console when the right panel is hidden.

Fixed an issue that showed an incorrect response code tab in API Console.

Fixed an issue that caused API Designer to report a problem with external XSD schemas.

OAS importer no longer generates an invalid RAML when an OAS definition names include special characters such as [.

Fixed an issue with creating a new file from the context menu of a folder.

Bumped the JS parser version to 1.1.13.

Bumped the API Console version to 3.0.13.

Importing an OAS 2.0 document is greatly improved and is no longer in Beta.

Fixed several minor issues with the import of an OAS 2.0 document.

Browser crashes when adding a { after a resource name in RAML 0.8.

Fixed minor issues around tracing the corrects errors across multiple files.

Fixed other parsing issues.

Bumped the JS parser version to 1.1.12.

Bumped the API Console version to 3.0.12.

Several mocking service issues.

In the previous version, the baseUri was duplicated after quitting the designer with the mocking service enabled.

Improved main menu.

Bumped JS parser version to 1.1.8.

Bumped API Console version to 3.0.11.

The mocking server no longer returns “unknown type” when type is defined in a library.

In the previous versions, importing files did not get automatically saved. This release fixes that issue and also eliminates the confusing error indicator that appeared after import in a valid RAML file.

Improved warnings and trace information for better error management.

Auto-completion for any named variable such as paging trait or collection resource type across all RAML typed fragments.

Validation of RAML 1.0 typed fragments.