2.0.0-BETA2

JDK 11 release for feedbacks.

1.5.25

upgrade json-schema-form to 0.1.26

1.5.24

1.5.24 (2018-12-15)

Full Changelog

Fixed bugs:

• OpenAPI validation does not fail when incorrect types are passed in the Request Body #64

Merged pull requests:

• made changes based on comments of #65 #66 (BalloonWen)
• Fixed #64 #65 (BalloonWen)

1.5.23

1.5.23 (2018-12-01)

Full Changelog

Merged pull requests:

• OpenApiHelper class will not fail when the optional servers section is not provided #63 (zabooma)

1.5.22

1.5.22 (2018-11-10)

Full Changelog

Closed issues:

• Configured class: com.foo.reportListener.handler.SpecYamlGetHandler has not been found #61

1.5.21

1.5.21 (2018-10-26)

Full Changelog

Implemented enhancements:

• add an endpoint to serve swagger-ui for manual testing #30

Upgrade Guidelines:

• This is a release to fix defects and add features so it is backward compatible. Just update the version in your pom.xml should work.

1.5.20

1.5.20 (2018-10-05)

Full Changelog

Closed issues:

• Handler needs to properly escape characters in the Status description #60
• update default validator.yml and security.yml to framework specific #59
• schema validation does not work for boolean query parameter #57

Upgrade Guidelines:

• This is a release to fix defects and add new features so it is backward compatible.
• A bug has been fixed in json-schema-validator, please upgrade it to version 0.1.23
• For this release, we have introduced the framework specific security configuration to enable/disable JwtVerifyHandler. Depending on which framework you are using it might be swagger-security.yml or openapi-security.yml and here is an example.

# Enable JWT verification flag.
enableVerifyJwt: true

# Enable JWT scope verification. Only valid when enableVerifyJwt is true.
enableVerifyScope: true

The old security.yml is still in use to control how JwtHelper will behave. It also set enableVerifyJwt to true for backward compatibility if framework specific security config is not there.

1.5.19

1.5.19 (2018-09-22)

Full Changelog

Closed issues:

• openapi-validator doesnot validate enum values from the specification #56
• upgrade to the new open-parser api for openapi-validator #54
• switch to http-string module for HttpString headers constants #53
• Error parsing openapi spec when objects depend on eachother #52
• support YAML format for the specification in OpenAPI framework #51

Merged pull requests:

• Implements OpenApiEndpointSource and SwaggerEndpointSource which … #55 (logi)

Upgrade Guidelines:

• A defect in OpenAPI 3.0 validator is fixed and this can cause a previously passed validation test case fails.
• You can use openapi.yaml for light-codegen now and the same file will be used at runtime. If only validation changes for the spec, just copy it to the application config.
• The security.yml and validator.yml should be renamed to swagger-security.yml, swagger-validator.yml, openapi-security.yml and openapi-validator.yml for future proof. The generic files are still working.

1.5.18

1.5.18 (2018-08-16)

Full Changelog

Closed issues:

• Fix issue causing null pointer exception when required field missing from requestBody #48
• flatten the config files into the same directory for k8s #47
• support specific swagger or openapi security and validator configuration #45
• upgrade to undertow 2.0.11.Final #44

Merged pull requests:

• Fixing issue causing required field to be required in requestBody #49 (NicholasAzar)
• fixes #45 support specific swagger or openapi security and validator … #46 (stevehu)

1.5.17

bot checkin