Swagger-parser 1.0.15 Released!

This release updates the underlying swagger-core library to 1.5.6.

Notable fixes

• Fixed NPE with references #150
• void response type for converted specs #140

Swagger-parser 1.0.13 Released!

This itty-bitty release provides proper feedback when an invalid (i.e. unparseable) swagger is specified. Required for the swagger-inflector release!

Swagger-parser 1.0.12 Released!

A small number of important enhancements have been added to the Swagger Parser. The parser now supports and resolves shared components throughout the swagger definition.

Notable Features

• Support for file:// protocol (#125)
• Added support for top-level, shared parameters, responses (#122)

Notable bug fixes

• Addressed issue with duplicate parameters shared across operations (#126)
• Fixed parse issue with non multi-fromatted array parameters

Swagger-parser 1.0.11 Released!

A small number of important enhancements have been added to the Swagger Parser. Now you can parse Swagger definitions with inline models and with better error handling.

Notable Features

• Parsing is no longer a “single-shot” (#108)
• Feedback on invalid parsing (#106, #108)
• Support for inline schema parsing (#78)

Swagger-parser 1.0.10 Released!

Notable Features

• Refactor SwaggerResolver (#73) - thanks @Helmsdown!
  • Multiple Json and Yaml spec files that are referenced together
  • Relative file, URL, and internal file references
  • Performing the resolution in one pass over the swagger model tree
  • Caching contents of files (remote or relative) and resolved objects to avoid repeating expensive operations
  • Gracefully (as possible) handling conflicting reference names (more on this below)
  • Handling resolutions in all variants of Model, Property, and Parameter (e.g. ArrayModels, ArrayProperty, MapProperty, etc)
  • Handling multiple levels of references (e.g. a RefModel which when resolved has a RefProperty)
  • Separating the resolution logic for one type into is own class to hopefully make it easier to rationalize how that logic works and hopefully make it easier to test
  • Centralize shared logic (caching a value, get the contents of ref, json/yaml deserialization)

Swagger-parser 1.0.9 Released!

Notable Features

• Processing is done using UTF-8 - #67
• Add YAML support to the resolver - #69

Notable Bug Fixes

• Operations will now inherit consumes/produces from the API Declaration when converting from 1.X to 2.0 - #41
• Fixed SwaggerParser.parse(String swaggerAsString) behavior - #59
• Fixed conversion for void response type from 1.X to 2.0 - #60

Swagger Parser 1.0.8

Minor bug-fixes and

• Fixed reading of line-breaks: #35
• Fixed invalid accept header when reading remote Swagger definitions: #51
• Updated dependencies and according packages from com.wordnik to io.swagger: #57
• Added license and reformatted code in accordance with https://github.com/swagger-api/swagger-core/wiki/Coding-Standards

Swagger Parser 1.0.6

More minor bug-fixes and improvements:

• Added handling of unrecognized HTTP Methods: swagger-api/swagger-codegen#612
• Added accept header to HTTP requests for Swagger definitions: e364cb7
• Added convenience method to parse Swagger model from preloaded string: #39
• Excluded logback.xml per swagger-api/swagger-codegen#689
• Improved handling of unknown properties and old method property name #43

Swagger Parser 1.0.5

This is a minor bug-fix release:

• Fixed issue with path parameter parsing; #31
• Fixed issue with void responses treated as models: #34
• Fixed issue with repeat references: #33

As always - thanks to everyone helping out!

Swagger Parser 1.0.3 Released!

Bug fixes and enhancements:

• Fix NPE with null return type
• fixed issue where default value is not preserved when converting specs #20
• newlines lost when reading YAML #23
• use utf-8 encoding #21
• avoid parsing non-swagger objects. Now you must have "swagger": "2.0" in your JSON #19