[JavaPlayFramework] Add parameters for beanValidation in the application.conf + fix bugs (#6794)

* Add configuration to split input and output bean validations. When useBeanValidation is used, the variable are created in the application.conf file and can be tweaked by environment. For example, dev and stage can have true to both but only have input in prod.

* Refactor of mustache tags for more clarity

* sample generation with refactor

* Fix a couple of bugs with the fake-endpoint yaml but there is still 2 cases where it doesn't work.
This commit is contained in:
Jean-François Côté
2017-10-27 10:48:27 -04:00
committed by wing328
parent cab4fc0fed
commit 18ba90f5ac
124 changed files with 784 additions and 1251 deletions

View File

@@ -17,6 +17,15 @@
play.filters.headers.contentSecurityPolicy=null
# When using bean validation with the swagger api, the validator will check that every constraint is respected
# This is very useful when testing but could add a lot of overhead if you return a lot of data. Benchmark have
# shown that the time it takes to validate is exponential.
# If this is a concern in your application, or if you don't want to validate the output coming from your API for
# respecting its contract, set the "output" property below to "false". Since there is not a lot of data as input for
# an endpoint, I highly suggest you let the "input" property set to true.
useInputBeanValidation=true
useOutputBeanValidation=true
## Akka
# https://www.playframework.com/documentation/latest/ScalaAkka#Configuration