Finatra provides a simple validation framework inspired by JSR-303.
The validations framework integrates Finatra's custom case class deserializer to efficiently apply per field validations as request parsing is performed. The following validation annotations are available (and additional validations can be easily created):
@CountryCode@FutureTime@PastTime@Pattern@Max@Min@NotEmpty@OneOf@Range@Size@TimeGranularity@UUID@MethodValidation
A method validation is a case class method annotated with @MethodValidation which is intended to be used for validating fields of the cases class during request parsing. Reasons to use a method validation include:
- For non-generic validations.
@MethodValidationcan be used instead of defining a reusable annotation and validator. - Cross-field validations (e.g. startDate before endDate)
For an example see the Car test case class. Additionally, see the CommonMethodValidations for pre-defined commonly useful method validations.
By default validation errors are returned alphabetically sorted by validation error message (for determinism when testing). See the CaseClassMappingException.
Eg.,
{
"errors" : [
"location.lat: [9999.0] is not between -85 and 85",
"location.long: field is required",
"message: size [0] is not between 1 and 140",
"nsfw: 'abc' is not a valid boolean"
]
}You may desire to execute validation for specific case classes in certain scenarios, but bypass validation in others. For example, you may want to validate a POST request on the write path and store the JSON results somewhere, but bypass validating that same JSON for a GET request on the read path.
You can create a FinatraObjectMapper that will bypass validation like this:
def create(injector: Injector = null): FinatraObjectMapper = {
val jacksonModule = NullValidationFinatraJacksonModule
new FinatraObjectMapper(
jacksonModule.provideScalaObjectMapper(injector))
}