Validation and Type Conversion (DP3)

[shimks]

Epic

As a LoopBack4 user, I would like to have validation for my server requests and responses as defined in my spec.

More information

• Validation and type-conversion of input arguments in the REST layer

  • query/path/headers/form parameters
  • request body - content-type, e.g. application/json, application/xml,
  • validate against:
    • whether the property exists
    • simple type vs complex type (combined validation of various properties)

• Validation and type-conversion for Model and database tier

DP3 scope

• deserialize HTTP parameters based on OpenAPI spec - see Use OpenAPI v3 spec to coerce primitives in query, path and headers #750
• minimal validation of input parameters at REST layer - see Router: validate input parameters #118

Out of scope

• extensibility of coercion and validation - see Allow coercion and validation to be extensible #1343

[jannyHou]

We have two more stories left for this epic:

• Leveraging ajv to validate input parameters from requestBody: Router: validate input parameters #118
• Add jsonDef or OpenAPI schema for internal types in @loopback/repository: Generate OpenAPI schema for Model properties of built-in JavaScript/Node.js types #1112

cc @bajtos

[bajtos]

Thank you @jannyHou.

Add jsonDef or OpenAPI schema for internal types in @loopback/repository: #1112

We have removed this task from DP3 two weeks ago, I'll move it to the GA Epic for Validation/Coercion.

[dhmlau]

Closing as done.