Releases: swagger-api/swagger-parser
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!
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
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
Notable Bug Fixes
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