Avoid defining so many JSON models (swagger, joi, mongoose...)

Typical app with API, entities and ORM would have to define the models in 3 different and equivalent places: swagger for API, json-schema/Joi for entities, some ORM-specific format (e.g. moongoose or sequelize models). Adding a new field? add 3 times... doesn't make senseIs someone familiar with a technique to define models schema once, hopefully with json-schema, and generate API docs based on that?

Submitted April 15, 2018 at 07:44PM by yonatannn