Validator middleware for the middy framework, the stylish Node.js middleware engine for AWS Lambda
This middleware automatically validates incoming events and outgoing responses against custom schemas defined with the JSON schema syntax.
If an incoming event fails validation a BadRequest
error is raised.
If an outgoing response fails validation a InternalServerError
error is
raised.
This middleware can be used in combination with
httpErrorHandler
to automatically return the right
response to the user.
It can also be used in combination with httpcontentnegotiation
to load localised translations for the error messages (based on the currently requested language). This feature uses internally ajv-i18n
module, so reference to this module for options and more advanced use cases. By default the language used will be English (en
), but you can redefine the default language by passing it in the ajvOptions
options with the key defaultLanguage
and specifying as value one of the supported locales.
Also, this middleware accepts an object with plugins to be applied to customize the internal ajv
instance. Out-of-the-box ajv-i18n
and ajv-formats
are being used.
To install this middleware you can use NPM:
npm install --save @middy/validator
inputSchema
(object) (optional): The JSON schema object or compiled ajv validator that will be used to validate the input (request.event
) of the Lambda handler.outputSchema
(object) (optional): The JSON schema object or compiled ajv validator that will be used to validate the output (request.response
) of the Lambda handler.ajvOptions
(object) (optional): Options to pass to ajv class constructor. Defaults are{ strict: true, coerceTypes: 'array', allErrors: true, useDefaults: 'empty', messages: false, defaultLanguage: 'en' }
.
NOTES:
- At least one of
inputSchema
oroutputSchema
is required. - Important Compiling schemas on the fly will cause a 50-100ms performance hit during cold start for simple JSON Schemas. Precompiling is highly recommended.
- Default ajv plugins used:
ajv-i18n
,ajv-formats
,ajv-formats-draft2019
- If you'd like to have the error details as part of the response, it will need to be handled separately. You can access them from
request.error.details
, the original response can be found atrequest.error.response
.
Example for input validation:
import middy from '@middy/core'
import validator from '@middy/validator'
const handler = middy((event, context) => {
return {}
})
const schema = {
required: ['body', 'foo'],
properties: {
// this will pass validation
body: {
type: 'string'
},
// this won't as it won't be in the event
foo: {
type: 'string'
}
}
}
handler.use(validator({
inputSchema: schema
}))
// invokes the handler, note that property foo is missing
const event = {
body: JSON.stringify({something: 'somethingelse'})
}
handler(event, {}, (err, res) => {
t.is(err.message,'Event object failed validation')
})
Example for output validation:
import middy from '@middy/core'
import validator from '@middy/validator'
const handler = middy((event, context) => {
return {}
})
const schema = {
required: ['body', 'statusCode'],
properties: {
body: {
type: 'object'
},
statusCode: {
type: 'number'
}
}
}
handler.use(validator({outputSchema: schema}))
handler({}, {}, (err, response) => {
t.not(err, null)
t.is(err.message,'Response object failed validation')
expect(response).not.toBe(null) // it doesn't destroy the response so it can be used by other middlewares
})
For more documentation and examples, refers to the main Middy monorepo on GitHub or Middy official website.
Everyone is very welcome to contribute to this repository. Feel free to raise issues or to submit Pull Requests.
Licensed under MIT License. Copyright (c) 2017-2021 Luciano Mammino, will Farrell, and the Middy team.