Swagger-Parser 1.0.26 Released!

Some minor updates in the parser to support the swagger-core 1.5.12 release.

Improvements

• Better parsing of BodyParameter. Support extensions #360, #381
• Update HTTP client library to more secure version #397
• Show SSL errors more gracefully #383

Fixes

• No longer converting minimum, maximum, default values to double when parsing. Now uses BigDecimal along with a string cache to keep the original formatting without interpolation #400

Swagger-parser 1.0.25 Released!

Well what do you know, a late holiday gift! Here's a new release of swagger-parser to bring you into the New Year the right way.

Enhancements

• Updated to Jackson 2.8.4, along with the latest swagger-core
• Parsing of non-string enum values #363
• URL cleaning to support 1.1, 1.2 specs #367
• Parsing of uniqueItems, multipleOf #372
• Less printlns #370

Fixes

• allOf with single element no longer gives error #371

Swagger-parser 1.0.23 Released

So many updates! 1.0.23 brings a ton of fixes and enhancements when dealing with everyone's favorite dinner-time topic: JSON References. Yes now, we are correctly traversing from host-to-host, from relative-to-absolute, etc. It's a blast to follow along with the tests, so check them out! (Note there is very little difference between a bug fix and enhancement, so consider the selection between the two to be pretty much random)

Bug Fixes:

• Fixed NPE when parsing shared path parameters #268
• Nested references are now correctly resolved #270
• No more duplication of path parameters #271
• Incorrect vendor extensions in remote references #274
• Now correctly resolving nested references in arrays #286
• Correct escaping of JSON Pointers #289
• Collection type format parsing was incorrect #291, #292

Enhancements:

• Better detection of content type--no longer using extensions #276
• Resolution of recursive references #278
• Resolving direct model references now supported #297
• Resolution of external files in folders now supported #299, #304, #306, #312, #314
• Resolution of remote -> relative references across hosts is now supported #316, #319, #325, #330

Swagger-parser 1.0.16 Released!

Fixed a small glitch where type checking may not behave as expected #159

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