WARNING: DO NOT USE IT IN YOUR PRODUCTION ENVIRONMENT BEFORE 1.0.0.

Installation

npm install -S egg-swagger-validate

# and its dependencies
npm install -S egg-validate

Usage

Import it and its dependencies via config/plugin.js:

module.exports = {
  ...

  'validate': {
    enable: true,
    package: 'egg-validate'
  },
  'swagger-validate': {
    enable: true,
    package: 'egg-swagger-validate'
  }

  ...
}

Config it via config/config.<env>.js:

module.exports = {
  ...

  swaggerValidate: {
    swaggerFile: '/absolute/path/to/swagger/file'
  }

  ...
}

Extentions to the Swagger Schema

Why?

It is NOT one-to-one mapping of Swagger Schema parameters' type to egg-validate's type. Therefore, we have to find a way to do this.

Swagger specification said:

Allows extensions to the Swagger Schema. The field name MUST begin with x-, for example, x-internal-id.

So, I extend it.

Extensions

Extensions of Parameter Object:

• x-format corresponding to type in parameter
• x-format-options corresponding to other fields except type in parameter
• x-controller bind a controller to current path automatically

Do not use app/router.js in egg.js, if you start to use x-controller.

More information of available value of x-format and x-format-options can be found in parameter's document.

Extentions to egg-validate

Why?

egg-swagger-validate will check multiple types of parameters at one time, different from what egg-validate does. Therefore, we have to find a way to distinguish different types of validate error.

Extensions

Extensions of egg-validate:

• Add in field for errors.

For example, when using egg-validate, the response is:

{
    "code": "invalid_param",
    "errors": [
        {
            "code": "missing_field",
            "field": "quantity",
            "message": "required"
        }
    ],
    "message": "Validation Failed"
}

But, when using egg-swagger-validate, the response is:

{
    "code": "invalid_param",
    "errors": [
        {
            "code": "missing_field",
            "field": "quantity",
            "in": "query",
            "message": "required"
        }
    ],
    "message": "Validation Failed"
}

You can see, in field let you know where the missing field in.

Functions of egg-swagger-validate

1. generates validate rules from x-format and x-format-options
2. validate parameters according to rules generated from step 1
3. if not pass, throw error
4. if pass, handle request by using controller specified by x-controller

Example of extended Swagger Schema

...

paths:
  /mails:
    get:
      summary: get mails
      description: Get Mails
      parameters:
        - name: email
          in: query
          description: email address
          required: true
          type: string
          x-format: email
        - name: quantity
          in: query
          description: quantity of emails
          required: true
          type: number
          x-format: number
          x-format-options:
            max: 20
            min: 1
      x-controller: mails.get

...

Last

Sit here, code this.