Rejecting bad input before it reaches the database. While this can be done manually inside a handler, there are solutions in place to derive type, range, enum and mandatory checks from the model definitions.
Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP
Enforces @mandatory, @assert.range, @assert.format, @assert.target and @assert with a CXL case expression whenever data is written: the static checks on the input, the expressions collected into one query and run in the database, and a failure rejects the request and rolls the transaction back.
A Node.js coverage assessment has not been written. View all flavors
Adds a second declarative vocabulary beside the model's own assertions: JSON Schema draft-07 keywords, annotated per element and checked on the way in, for the types and formats CDS does not express.
Overrides what a failed validation returns to the client: the message per element, resolved from the i18n bundle and able to interpolate values from the record, and a handler class whose isValid decides, with the target worked out by the plugin and the errors collated.
A Node.js coverage assessment has not been written. View all flavors
Neither the package manifest nor the repository tree declares a licence.
@assert.range accepts open intervals, a min or max wrapped in parentheses, and an underscore for infinity. Before this release a range was a closed [min, max] and a one-sided bound needed a case expression or a handler. CAP Java gained the same in 3.5.0.
Advice that @assert.range cannot express 'strictly positive' or an unbounded side, and the before handlers written for that.
capability:input-validation