- Better handling of references to invalid objects (Issue #120, #121)
- Fix bug validating models with a
defautlattribute (Issue #124) - Fix bug validating models without properties (Issue #122)
- swaggerMetadata middleware now converts paramters to their appropriate type (Issue #119)
- swaggerRouter middleware now handles void responses for mock mode (Issue #112)
- swaggerRouter middleware now wraps controller calls in try/catch block and sends errors downstream via
next(Issue #123) - swaggerSecurity middleware now sends authentication/authorization errors downstream via
next(Issue #117) - swaggerSecurity middleware now handles API Key authentication/authorization (Issue #128)
- swaggerUi middleware now allows you to serve your own custom swagger-ui resources (Issue #111)
- Attached the original data sent to
res.endto response validation errors (Issue #110) - Response validation for Swagger 2.0 now takes the default response into account when validating (Issue #99)
- Removed requirement for servers to wire up body/query string parsers (We default to body-parser and qs respectively.) (Issue #70)
- Updated the version of Z-Schema being used to fix some browser issues (Issue #94)
- Updated to build/test the browser using
gulpgulp test(Issue #96) - Specification APIs for Swagger 2.0 now do a full validation prior to performing the business logic behidn the API (Issue #97)
- Fixed Quick Start documentation example (Issue 101)
- Fixed a bug in the CLI where local YAML files were not processed properly (Issue #104)
- Fixed a bug where erroneous validation errors were thrown for valid files due to paths with path paramters and vendor extensions (Issue #103)
(Contained only upstream release changes)
- Added API/CLI for Swagger 1.2 to 2.0 conversion (Issue #41)
- Fix browser build (Issue #90)
- Properly support Swagger 2.0 form parameters (Issue #88)
- Support validating responses (Issue #25)
(Contains breaking changes)
- Add an API (
Specification#resolve) to get all of or part of a Swagger document as fully resolved (Issue #63) - All
SpecificationAPIs now require an error-first callback as the last argument - Fix support for header parameters where case caused an issue (Issue #82)
- Make sure tests that were async were written properly (Issue #65)
- Middleware now requires you to use the
initializeMiddlewarefunction during server initialization to validate your Swagger document(s) and return the appropriate middlewares (Issue #77) - Refactor to support upstream path-level authorizations in Swagger 1.2 (Issue #27)
- Support path parameters that are not path segments (Issue #72)
- Support references throughout the Swagger 2.0 document (Issues: #38, #55, #68, #73, #79)
- Support remote reference (Issue #54)
- Support Swagger 2.0 security (Issue #69)
- Support validating remote files from the CLI (Issue #74)
- Support validating YAML files from the CLI (Issue #75)
- Switched from jjv+jjve for JSON Schema validation to ZSchema
- Validate situation in Swagger 1.2 where the model id and the model's
idfield are not the same (Issue #71) - When printing out validation errors/warnings, support inner errors/warnings (Issue #85)
- Various minor bug fixes that did not result in issues
- Various documentation/example fixes to support the changes above