Api Elements.js Versions Save

Enhancements

• Compatibility with Fury 3.0.0 Beta 14.

Enhancements

• Compatibility with Fury 3.0.0 Beta 14.

Enhancements

• Compatibility with Fury 3.0.0 Beta 14.

Enhancements

• Compatibility with Fury 3.0.0 Beta 14.

This release contains an updated api-elements models. See api-elements 0.2.4 for further details.

Enhancements

• Added hosts properties on Resource and Transition to access the "hosts" resources stored in the element attributes. Cateogory elements contain hosts so that you can access hosts categories from the "api" category.

Enhancements

• Adds support for termsOfService in 'Info Object'.
• Adds support for contact in 'Info Object'.

Bug Fixes

• Prevents an exception being raised when using freeze() on the parse result returned by the parser when the OpenAPI document uses a request header with multiple request/response pairs.

Enhancements

• Adds support for info.termsOfService. For example the following document:

  swagger: '2.0'
  info:
    termsOfService: http://example.com/terms/
  

  will add the link to the terms of service http://example.com/terms/

• Adds support for info.contact. For example the following document:

  swagger: '2.0'
  info:
    url: http://www.example.com/support
    email: [email protected]
  

  will add a link to the contact URL and a second link to the contact email

Bug Fixes

• This release includes performance improvements to parsing documents which contain the same schema re-used via a reference ($ref) many times in request parameters and response bodies.

Bug Fixes

• Prevents a 'Path Item Object' from being included in a Resource Group created by an 'Operation Object' in a previously defined 'Path Item Object'.

• Optional parameters will now include an optional typeAttribute in the parse result. This will fix conversion to API Blueprint with fury-cli where optional parameters have shown up as required in the generated API Blueprint.

• Allows generating of JSON bodies for schemas which make use of allOf and include circular references. Under some circumstances this would previously fail, and a warning may have been emitted "Unable to generate application/json example message body out of JSON Schema"