A module that sits independently between the controller and the model, performing request data validation, serialization and integrity checks
npm install forensic-handler
!npm
Handler is a NodeJS package that sits independently between the controller and the model, and asynchronously performs request data validation, serialization and database integrity checks. It has excellent error reporting with wide range of validation rules. It can be used with relational and non-relational databases/ORMs.
All validation rules are defined in plain JS objects. Handler supports Mongoose Models by default when working with non-relational databases such as MongoDB and also supports Sequelize Models by default when working with relational databases such as Postgres, Mysql, etc.
It is also extensible, customizable so that you can define more custom validation rules if there is need for it.
- Dealing With Multi-Value Fields and Files
- Specifying Accepted File Mime Types
- Conditional Require & Data Override
- Ondemand Data Handling and Update
- Data Expansion & Compaction for NoSQL
Install via npm:
``bash`
npm install --save forensic-handler
before working with development version of this project and running test, you need to setup mysql database and connection credentials, and also Mongodb. create a .env file for setting up your mysql database credentials and add the following env settings:
1. DB_USER, database user
2. DB_PSWD, user database password
3. DB_NAME, your test database name (likely test)
The Handler:
`typescript
import Server from 'r-server'; // import rserver
import Handler from 'forensic-handler';
import UserModel from './models/UserModel'; //import model
import bcrypt from 'bcrypt';
const app = Server.create(); // create server instance
app.post('/signup', async (req, res) => {
const handler = new Handler(req.data, req.files, {
email: {
type: 'email',
checks: {
if: 'exists',
model: UserModel,
err: 'email address already exists',
},
},
password1: {
type: 'password',
postCompute: async function(password) {
return await bcrypt.hash(password, Number.parseInt(process.env.SALT_ROUNDS));
},
},
password2: {
type: 'password',
shouldMatch: 'password1',
},
});
if (await handler.execute()) {
const data = handler
.model()
.skipFields('password2')
.renameField('password1', 'password')
.export();
const user = await UserModel.create(data);
handler.data.id = user.id;
}
if (handler.succeeds()) {
return res.json({
status: 'success',
data: {
id: handler.data.id,
},
});
} else {
return res.json(
{
status: 'failed',
errors: handler.errors,
},
400
);
}
});
app.listen(null, () => {
console.log('listening');
});
`
Validation rules are defined as JavaScript plain object keyed by the field names. Each field rule object can contain the following rule properties:
1. type: indicates the type of validation to carry out on the field. it defaults to text.
2. required: indicates if the field is required. defaults to true.
3. defaultValue: specifies the default value for a non required field. it defaults to empty string.
4. filters: defines filter rules to apply to the field value(s) prior to validations, such as case conversion, type casting, html tag stripping, etc.
5. checks: defines database integrity check or array of database integrity checks to run on the field value(s).
6. options: defines extra validation options specifically for the field.
7. requiredIf: defines a conditional clause, which if satisfied, makes the field required, else the field becomes optional.
8. overrideIf: defines a conditional clause, which if satisfied, will override a field's raw data value, else the field value is retained.
To reference a validation principal, the convention used is to enclose the principal field name in curly braces within a string . '{field-name}'. The module will find and resolve such, replacing it with the field value.
There are certain placeholder formats that can be used to refrence certain values. This includes {this} which references the current field value under validation; {_this} references the current field name under validation while {_index} references the current field value index position (in the case of validating array of fields).
Moreover, there is the {CURRENT_DATE}, {CURRENT_YEAR}, and {CURRENT_TIME} that references the current date, current year and current timestamp values respectively.
Example:
`typescript
const rules = {
//validate first name. should be at least 3 characters
'first-name': {
options: {
min: 3,
minErr: '{_this} should be at least 3 charaters length',
},
},
//validate last name. should be at least 3 characters
'last-name': {
options: {
min: 3,
minErr: '{_this} should be at least 3 charaters length',
},
},
//validate middle name. should be at least 3 characters. it is optional
'middle-name': {
required: false,
options: {
min: 3,
minErr: '{_this} should be at least 3 charaters length',
},
},
//we are expecting an array of favorite colors
'favorite-colors': {
type: 'choice',
filters: {
//convert the colors to lowercase
toLower: true,
/* we can also supply a callback function/
callback: value => value.toLowerCase(),
},
options: {
choices: ['green', 'white', 'blue', 'red', 'violet', 'purple'],
err: 'color {_index} is not a valid color',
},
},
// this is a checkbox type
'subscribe-newsletter': 'checkbox',
//email is required if user checks the subscribe checkbox,
email: {
type: 'email',
err: '{this} is not a valid email address',
requiredIf: {
if: 'checked',
field: 'subscribe-newsletter',
},
},
};
`
Filters are applied to the field values prior to validations. You can use filters to modify field values prior to validation. The available filters include:
1. decode: determines if decodeURIComponent() method should be called on the field value. defaults to true
2. trim: determines if String.prototype.trim() method should be called on the field value. defaults to true
3. stripTags: determines if html tags should be stripped out from the field value(s). Behaves like PHP's strip_tags(). Defaults to true
4. stripTagsIgnore: Defines array of html tags that should not be stripped out if stripTags filter is set to true. defaults to empty array. It can also be a string of comma or space separated html tags, rather than array.
5. numeric: determines if the field value(s) should be cast to float. if the value is not numeric, it is cast to 0. defaults to false.
6. toUpper: determines if the field value(s) should be turned to uppercase. defaults to false
7. toLower: determines if the field value(s) should be turned to lowercase. defaults to false
8. capitalize: determines if the first character of each field value should be uppercased, while others are lowercased. defaults to false. eg, given field value of lonDON, it is converted to London.
9. minimize: determines if the field value should be minimised, with empty lines stripped out, and each line trimmed. This is handy when accepting computer processed values such as html text, markdown text, css text etc.
10. callback: a callback function to execute. The callback method accepts the field value, performs some modifications, and returns the result of the operations.
` ', ' typescript`
const rules = {
country: {
filters: {
toLower: true //convert to lowercase
}
},
comment: {
filters: {
stripTagsIgnore: ['p', 'br'] // or ['
'] or 'p, br' or '
', etc
}
},
description: {
filters: {
callback: (value) => value, //do some modifications and return the result
}
}
];
The module defines lots of validation types that covers a wide range of validation cases that includes the following:
The limiting rule validation options touches every validation. It is where we can define the limiting length of a string, date or numeric values. These includes the min, max, gt (greater than) and lt (less than) options.
`typescript`
const rules = {
'first-name': {
//type defaults to text
options: {
min: 3,
minErr: 'first name should be at least 3 characters length',
max: 15
}
],
'favorite-integer': {
type: 'pInt',
options: {
'lt': 101, //should be less than 101, or max of 100.
}
},
'date-of-birth': {
type: 'date',
options: {
min: '01-01-1990', //only interested in people born on or after 01-01-1990
max: '{CURRENT_DATE}'
}
},
};
It is quite easy to carry out different flavours of regex rule tests on field value(s). There are four kinds of regex rules. These include regex, regexAny, regexAll, and regexNone tests.
For regex test, it must match the test, otherwise it is flagged as error. For regexAny, at least one of the tests must match. For regexAll, all regex tests must match. For regexNone, none of the regex tests should match.
`typescript
const rules = {
'first-name': {
options: {
regexAll: [
//name must start with letter
{
pattern: /^[a-z]/i,
err: 'name must start with an alphabet',
},
//only aphabets, dash and apostrophe is allowed in name
{
pattern: /^[-a-z']+$/,
err: 'only alphabets, dash and apostrophe is allowed in names',
},
],
},
},
country: {
options: {
regex: {
//we expect two letter country code.
pattern: /^[a-z]{2}$/,
err: '{this} is not a 2-letter country iso-code name',
},
},
},
'phone-number': {
options: {
regexAny: {
//array of tests, we are ok if any of the test matches, else flag error
patterns: [
//phone number can match nigeria mobile number format
/^0[0-9]{3}[-\s]?[0-9]{3}[-\s]?[0-9]{4}$/,
//phone number can match uk mobile number format
/^07[0-9]{3}[-\s]?[0-9]{6}$/,
],
err: 'only nigeria and uk number formats are accepted',
},
},
},
'favorite-colors': {
options: {
//we dont accept black nor white colors.
//note that we could combine the regex. just for example purposes.
regexNone: [
//we dont accept white as a color
{
pattern: /^white$/i,
err: '{this} is not an acceptable color',
},
//we dont accept black either
{
pattern: /^black$/i,
err: '{this} is not an acceptable color',
},
],
},
},
};
`
This rule is handy when you want to make sure that a field's value matches another field's value such as in password, email and phone number confirmation cases.
`typescript`
const rules = {
password1: 'password',
password2: {
type: 'password',
shouldMatch: 'password1',
},
};
To validate dates, set the type property to _'date'_. You can specify limiting rules that validates if the date is within a given limited range.
`typescript`
const rules = {
'date-of-birth': {
type: 'date',
options: {
min: '01-01-1990', //only interested in people born on or after 01-01-1990
max: '{CURRENT_DATE}',
},
},
};
To validate field as a range of values, set the type property to range. The range type accepts three more options keys, which are from, to and the optional step key that defaults to 1.
`typescript
const rules = {
day: {
type: 'range',
options: {
from: 1,
to: 31,
},
},
month: {
type: 'range',
options: {
from: 1,
to: 12,
},
},
year: {
type: 'range',
options: {
from: 1950,
to: '{CURRENT_YEAR}',
},
},
even-number: {
type: 'range',
options: {
from: 0,
to: 100,
step: 2,
err: '{this} is not a valid even number between 0-100'
},
},
even-alphabet: {
type: 'range',
options: {
from: 'A',
to: 'Z',
step: 2,
err: '{this} is not a valid even alphabet between A-Z'
},
}
};
`
To validate field against a choice of options, set the type property to choice. Acceptable options are specified using the choices property as array. The range type makes use of this type validator internally.
`typescript`
const rules = {
country: {
type: 'choice',
options: {
choices: ['ng', 'gb', 'us', 'ca', 'de'], // array of country codes,
err: '{this} is not a valid country code',
},
},
};
To validate email addresses, set the type property to email.
`typescript`
const rules = {
email: 'email',
};
To validate url, set the type property to url. the schemes option is optional. It defines the list of acceptable schemes.
`typescript`
const rules = {
website: {
type: 'url',
options: {
schemes: ['https', 'http'],
mustHaveScheme: true, //false by default
},
},
};
To validate phone numbers, set the type property to number. This project relies of libphonenumber.js for validating phone numbers
`typescript`
const rules = {
country: {
type: 'choice',
options: {
choices: ['us', 'ng', 'de', 'ca', .....],
}
},
//we want the phone number to be a valid phone number for the selected country
phoneNumber: {
type: 'phone-number',
options: {
country: '{country}'
},
},
};
To validate numeric values, whether floating or integers, there are nice validation types defined for such cases. These include the following types: money, number, nNumber, pNumber, int, pInt, and nInt.
`typescript`
const rules = {
amount: 'money',
userId: 'pInt',
};
Password validation is more like text validation except that some limiting rules and regex rules were added. The default implementation is that passwords must be at least 8 charaters long, and 26 characters max. It must contain at least two alphabets and at least two non-alphabets. You can disable this by setting the preValidate option to false.
The current implementation looks like below
`typescript`
const rules = {
password: {
type: 'password',
preValidate: false,
},
};
The module can validate files, including the integrity of file mime types thanks to an external package (file-type). It offers wide flavours of file validation types such as image, video, audio, document, archive and finally the generic file validation type.
Use of file memory units are recognised such as kb, mb, gb and tb.
`typescript`
const rules = {
picture: {
type: 'image',
options: {
min: '50kb',
},
},
};
You can define an absolute path to move the file to using the moveTo option. The file will be moved to the given location, with a hashed name computed for it. The hashed name is stored in the data property keyed in by the field name.
`typescript
import Server from 'r-server'; // import rserver
import Handler from 'forensic-handler';
import UserModel from './models/UserModel'; //import model
import * as path from 'path';
const app = Server.create(); // create server instance
app.post('/profile-picture', async (req, res) => {
const moveTo = path.join(__dirname, '../uploads/images/profile-pictures');
const handler = new Handler(req.data, req.files, {
picture: {
type: 'file',
options: {
moveTo: path.join(__dirname, '../uploads/images/profile-pictures');
}
}
});
if (await handler.execute()) {
await UserModel.findByIdAndUpdate(req.user.id, {
$set: {
profilePix: this.data.picture
}
}).exec();
}
if (handler.succeeds()) {
return res.json({
status: 'success',
data: {
profilePicture: handler.data.picture
}
});
}
else {
return res.json({
status: 'failed',
errors: handler.errors
}, 400);
}
});
app.listen(null, () => {
console.log('listening');
});
`
`typescript`
const rules = {
picture: {
type: 'image',
options: {
max: '400kb',
},
},
};
`typescript`
const rules = {
picture: {
type: 'audio',
options: {
max: '15mb',
},
},
};
`typescript`
const rules = {
picture: {
type: 'video',
options: {
max: '400mb',
},
},
};
Media files are one of image, audio and video.
`typescript`
const rules = {
picture: {
type: 'media',
options: {
max: '400mb',
},
},
};
`typescript`
const rules = {
picture: {
type: 'document',
options: {
max: '50mb',
},
},
};
examples of archives files are .zip, .tar.gz and .rar files.
`typescript`
const rules = {
picture: {
type: 'archive',
options: {
max: '100mb',
},
},
};
The handler can process multi-value fields and file fields. The field values are stored inside arrays after processing. Checkout RServer for multi-field value and files handling.
You can specify the accepted file extensions during validation. To specify accepted file extensions during file validations, use the exts option.
To specify accepted mimes, use the mimes options.
`javascript`
const rules = {
picture: {
type: 'file', //we could have used image, just for demonstration purposes
options: {
max: '400kb',
exts: ['jpeg', 'png'],
extErr: 'we only accept jpeg and png images',
},
},
};
We can conditionally make a field required or not required using the requiredIf option for the following conditions:
1. If another field is checked or not checked:
`typescript
const rules = {
'is-current-work': 'checkbox',
'work-end-month': {
type: 'range',
options: {
from: 1,
to: 12,
},
//if this is not user's current work, require the work-end-month
requiredIf: {
if: 'notChecked',
field: 'is-current-work',
},
//if this is user's current work, override work-end-month and set it to empty string
overrideIf: {
if: 'checked',
field: 'is-current-work',
with: '',
},
},
'subscribe-newsletter': 'checkbox',
email: {
type: 'email',
//if user decides to subscribe to our newsletter, require user email
requiredIf: {
if: 'checked',
field: 'subscribe-newsletter',
},
//if not, we override the email to empty string or null, even if email is supplied,
//it will not be picked
overrideIf: {
if: 'notChecked',
field: 'subscribe-newsletter',
with: '',
},
},
};
`
2. If another field equals or not equals a given value:
`typescript
const rules = {
country: {
type: 'choice',
options: {
choices: ['ng', 'us', 'gb', 'ca', 'gh'],
}
},
//if your country is not Nigeria, tell us your country calling code
countryCode: {
requiredIf: {
if: 'notEquals',
field: 'country'
value: 'ng',
}
},
//if you are in Nigeria, you must tell us your salary demand, other countries
//are paid a fixed $60,000 per annum
salaryDemand: {
type: 'money',
requireIf: {
condition: 'equals',
field: 'country',
value: 'ng',
},
overrideIf: {
condition: 'notEquals',
field: 'country',
value: 'ng',
with: '60000'
}
}
};
`
When carrying out update operations, it is always good that we update only the fields that are supplied.
Hence, there is the need to filter, pick out and process rules for only fields that are supplied without making other fields mandatory.
This is easily achieved by passing in true as the first argument to the execute method. If there is need to still make some fields mandatory, then we can pass those fields as second argument to the execute method.
The execute method signature is as shown below:
`typescript`
async execute(validateOnDemand: boolean = false, requiredFields: string[] | string = []): Promise
When working in NoSql databases, there is always the need to expand data during creation, and compact data during updates.
The export method of the Model module has this feature inbuilt. It will expand field data following the dot notation convention if the expandProperties argument is set as true (the default value).
`typescript
import Server from 'r-server'; // import rserver
import Handler from 'forensic-handler';
import UserModel from './models/UserModel'; //import model
import bcrypt from 'bcrypt';
const app = Server.create(); // create server instance
app.post('/signup', async (req, res) => {
const handler = new Handler(req.data, req.files, {
email: {
type: 'email',
checks: {
if: 'exists',
model: UserModel,
err: 'email address already exists'
}
},
password1: {
type: 'password',
postCompute: async function(password) {
return await bcrypt.hash(password, Number.parseInt(process.env.SALT_ROUNDS));
}
},
password2: {
type: 'password',
shouldMatch: 'password1'
},
'address.country': {
type: 'choice',
filters: {
toLower: true
},
options: {
choices: ['ng', 'de', 'fr', ...]
}
},
'address.street': 'text',
'address.zipCode': {
options: {
regex: {
pattern: /^\d{6}$/,
err: '{this} is not a valid zip code'
}
}
}
});
if (await handler.execute()) {
const model = handler.model().skipFields('password2').renameField('password1', 'password').export();
const user = await UserModel.create(data);
handler.data.id = user.id;
console.log(model.address.zipCode); // logs the zipCode etc
}
if (handler.succeeds()) {
return res.json({
status: 'success',
data: {
id: handler.data.id
}
});
}
else {
return res.json({
status: 'failed',
errors: handler.errors
}, 400);
}
});
app.listen(null, () => {
console.log('listening');
});
``