Permalink
Branch: master
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
78 lines (51 sloc) 2.39 KB

Fury OAS3 Parser Changelog

0.5.2 (19-02-19)

Enhancements

  • Added support for the nullable, description, default and example Schema Object properties.
  • Added support for response headers.
  • Added partial support for the example in Parameter Object
  • A warning will now be emitted when an invalid 'Parameter Object' 'in' value is set, previously this would cause an error.

Bug Fixes

  • Removed null as a valid type for a Schema Object, null is not supported as a type in OpenAPI 3 Schema Object. nullable should be used instead.
  • Added check for required in a Path Parameter.
  • The parser will now handle Responses Object which contains status codes that are not strings. Previously the parser would throw an error, we will now coerce number status codes to a string and emit a warning when a status code is not a string.

0.5.1 (30-01-19)

Bug Fixes

  • Fixes support for schema objects which do not declare a type.

0.5.0 (30-01-19)

Enhancements

  • Object properties in a Schema Object are now supported.
  • Referencing ($ref) a response object is now supported.
  • Array items in a Schema Object are now supported.
  • Object required properties in a Schema Object are now supported.
  • Request bodies and request body references are now supported in operations.

Bug Fixes

  • Fixed detection of YAML OpenAPI 3 documents where the OpenAPI version was not wrapped in quotes.

0.4.1 (28-01-19)

Enhancements

  • Path and query parameters are supported in 'Operation Object'

Bug Fixes

  • Unsupported properties in 'Parameter Object' will now emit an unsupported warning, previously using unsupported properties was emitting a warning that the properties were invalid.

  • The parser will no longer error out for unsupported parameter 'in' values, instead an unsupported warning will be emitted.

  • Parameter names containing unreserved URI Template characters (-, ., _, and ~) are now supported.

  • Referencing ($ref) a parameter that couldn't be parsed (due to the parameter failing validation) will no longer cause a cryptic error that the referenced object was not defined.

0.4.0 (25-01-19)

Enhancements

  • 'Request Body Object' are now supported, request body description and examples will be shown in the parse result.

Bug Fixes

  • The parser will warn when an OAS 3 document contains operation's with the same operationId.