JSON validace (json-validace) is an open source schema base validator that allows developers validate json and javascript object using an itiutive object schema.
There are alot of schema base validator packages out there but only a few supports nested validation, outside nested validation json-validace also has lots of useful methods, modifiers, types and many more feautures.
Just like any clasic npm package you can install json-validace using npm, yarn or any other installer you prefer.
# npm
npm install --save json-validace# yarn
yarn add json-validace // Filename: validace.schema.js
const jsonValidace = require("json-validace")
// create a validace schema
const loginSchema = new jsonValidace.Schema({
password: {
type: "string",
required: true,
minLength: 10,
maxLength: 20
},
email: {
type: "email",
required: true
}
})
// export loginSchema
module.exports = loginSchema// Filename: test.js
cosnt { loginSchema } = require('validace.schema.js')
// Useage
const result = loginSchema.validate({
email: "test@gmail.com",
password: "slickcodes"
})
// log result to console | terminal
console.log(result)# Result: in ternimal | console
{
error: null,
isValid: true,
data: { email: 'test@gmail.com', password: 'slickcodes' }
}if you're using REACT, VUE ,Svelte, Angular or other frontend framework you'll need to import using the import keyword.
import { Schema } from "json-validace"or
import jsonValidace from "json-validace"Properties & methods are the foundation of this library as they help specify the structure of the value expected. so far we have two types of Properties & methods namely Modifiers and Validators.
Validators are basically properties that allows you setup your prefered structure for every key par value.
- type
- required
- minLength & maxLength
- minNumber & maxNumber
- enum
- whitespace
- match
- validate
Default: no default value NOTE: this property is mandatory (required) Works with: all types of data Usage: type: "string"
the Type property is the only required property in the schema, it states what type of data is expected. The type property can be parsed as a property in the schema or directly.
// parse type directly
const { Schema } = require('json-validace')
const loginSchema = new Schema({
password: "string",
email: "email"
})// parse type as a key
const { Schema } = require('json-validace')
const loginSchema = new Schema({
password: { type: "string" },
email: { type: "email" }
})while declearing type directly can be simpler and easier to read, it doesnt allow you to parse in other keys, which is why it's good to set type as a key.
if the value parsed to the valdate method does not meet the type requirements the returned value will be populated with a type error.
const { Schema } = require('json-validace')
const loginSchema = new Schema({
password: { type: "string" },
email: { type: "email" }
})
// validate the login object
const validate = loginSchema.validate({
email: "slickcodes@mail", // this should be an email
password: 59489483 // this should be a valid string
})
console.log(validate)# BASH : result
{
error: {
password: { type: ' "password" value is not a string' },
email: { type: ' "email" value is not a email' }
},
isValid: false,
data: null
}
To prevent error message like the one above we'll need to parse in the correct type.
| S/N | Types | Example | Description |
|---|---|---|---|
| 1 | string | Hello Word | this is any sequence of character |
| 2 | test@gmail.com | email is a sub-type of string, it detects if the parsed value is a valid email address | |
| 3 | number | 59 | the number type checks if the parsed value is a valid number, NOTE: floats and any falsy or truty data are also considered as valid number. |
| 4 | float | 49.5 | floats is a sub-type of number and it checks if the value parsed in is a valid floating point number. |
| 5 | boolean | true | boolean is type checks if the parsed data is a valid boolean value, a good example can be using true, false or an expression like 59 > 3 |
| 6 | date | 1997-10-17 | date is a sub-type of string and it checks if the parsed data is a valid date type, it uses the YYYY-MM-DD configuration and it will work with any javascript date object like the date number (1671987916618) or (2022-12-25T17:05:33.957Z) |
| 7 | array | ["Paul", "Mike"] | array checks if the parsed in value is a valid array, depending on your schema you can also validate the value if the array is an array of object. |
| 8 | object | {author: "Paul"} | object type check if the data parsed is a valid object literal |
| 9 | jwt | eyJhbGciOiJIUzI1NiIsInR5c CI6IkpXVCJ9.eyJzdWIiOiI xMjM0NTY3ODkwIiwibmFtZSI6 IkpvaG4gRG9lIiwiaWF0Ij oxNTE2MjM5MDIyfQ .SflKxwRJSMeKKF2QT4fwp MeJf36POk6yJV_adQssw5c |
JWT (JSON Web Token) is a sub-type of string and it checks if the parsed string meets the JWT standard. |
| 10 | mongoid | 507f191e810c19729de860ea | the mongoId type is a sub-type of string and it checks if the string provided is a valid mongoID. |
Default: required: false Works with: all types of data works with: every type of data Usage: required: true (required: boolean)
when the required property takes in a boolean value, when this property is used, an error will be thrown if the parsed object does not have the key.
const { Schema } = require("json-validace")
// registering the login schema
const signupSchema = new Schema({
firstName: { type: "string", required: true },
lastName: { type: "string", required: true },
surname: { type: "string", required: false },
username: { type: "string", default: "anonymous" },
dateOfBirth: { type: "date", required: false },
gender: {
type: "string",
required: true,
}
})
// validating the login object
const result = signupSchema.validate({
firstName: "John"
})
console.log(result)# BASH: output
{
error: {
lastName: { required: '"lastName" feild is required!' },
gender: { required: '"gender" feild is required!' }
},
isValid: false,
data: null
}the above code shows us what happens with a required value is not parsed in. An error was only generate for the lastName and gender key, and other keys passed the check even though they where not provided. the firstName did not generate any error because it was provided.
works with: strings & arrays Usage: maxLength: 30 Usage: minLength: 8 Default: maxLength: Infinity; minLength: Infinity
The maxLength & minLength properties helps determin the length of the string or array provided. if the length of the value provided exceeds the maxLength then you'll get an error and if it's below the minLength you'll get an error.
const { Schema } = require("json-validace")
// registering the login schema
const loginSchema = new Schema({
email: { type: "email", required: true },
password: { type: "string", required: true, maxLength: 20, minLength: 8 }
})
// validating the login object
const result = loginSchema.validate({
email: "test@gmail.com",
password: "food" // length = 4
})
console.log(result)# BASH: output
{
error: {
password: { minLength: 'password should be 8 characters or above' }
},
isValid: false,
data: null
}The above code generated an error because the password did not meet the minLength requirement of 8 characters or below.
const { Schema } = require("./src")
const studentSchema = new Schema({
name: { type: "string", required: true },
id: { type: "number", required: true },
essey: {
type: "string",
required: true,
minLength: 500,
maxLength: 1000
},
hobbies: {
type: "array",
maxLength: 3
}
})
// validating the login object
const result = studentSchema.validate({
name: "John Doe",
id: 4934,
essey: "Introduction: Exercise is an essential part of a healthy lifestyle, and it offers numerous physical and mental benefits. Studies have shown that regular exercise can help reduce the risk of chronic",
hobbies: ["Football", "Video Games", "Coding", "Dancing"]
})
console.log(result)# BASH: Output
{
error: {
essey: { minLength: 'essey should be 500 characters or above' },
hobbies: { minLength: ' hobbies should be 3 items or below. ' }
},
isValid: false,
data: null
}the above code shows you how the minLength can also be used on arrays.
Default: no default value Works with: Boolean, Strings, JWT, mongoId, Number, Floats NOTE: this will not work with arrays object and date Usage: enum: ["rice", "mike", 4, true]
Enum ensures the provided value exist within a range of values. i found that this is useful when you want to specify things like the gender of a person.
const { Schema } = require("./src")
const studentSchema = new Schema({
name: { type: "string", required: true },
id: { type: "number", required: true },
favColor: {
type: "string",
enum: ["red", "green", "blue", "purple"]
}
})
// validating the login object
const result = studentSchema.validate({
name: "John Doe",
id: 4934,
favColor: "white"
})
console.log(result)# BASH: Output
{
error: {
favColor: {
enum: ' favColor should be an enum of (red | green | blue | purple)'
}
},
isValid: false,
data: null
}
Default: no default value Works with: Numbers and floats Usage: maxNumber: 20 Usage: minNumber: 10
maxNumber and minNumber are used to specify the number range allowed and will return an error if provided value does not meet the range, this is expecially useful when specifying age.
const { Schema } = require("./src")
const ageRange = new Schema({
age: {
type: "number",
required: true,
minNumber: 18,
maxNumber: 40
}
})
console.log(ageRange.validate({ age: 30 }))
console.log(ageRange.validate({ age: 10 }))
console.log(ageRange.validate({ age: 44 }))
console.log(ageRange.validate({ age: 18 }))# BASH: Output
{ error: null, isValid: true, data: { age: 30 } }
{
error: { age: { maxNumber: ' age is lower than 18' } },
isValid: false,
data: null
}
{
error: { age: { minNumber: 'age is higher than 40' } },
isValid: false,
data: null
}
{ error: null, isValid: true, data: { age: 18 } }###whitespace
whitespace returns an error if the provided string contains a space this is useful if you dont want text to be inside of a feild for example, the clasic username structure does not expect a space between it.Type: PropertyDefault: whitespace: trueWorks with: string, email,jwt,mongoidUsage: whitespace: true
####examples
const { Schema } = require('json-validace')
const login = new Schema({
username: {
type: "string",
required: true,
whitespace: false
},
password: {
type: "string",
required: true
}
})
const result = login.validate({
username: "slick codes",
password: "somesortofpassword"
})
console.log(result)# bash: Output
{
error: { username: { whitespace: 'username should have no whitespace' } },
isValid: false,
data: null
}match is great if you want to match a provided string against a regular expression. if the porvided string does not match the regular expression then it will return an error.
Type: PropertyDefault: no default valueWorks with: string, email,jwt,mongoidUsage: match: /^(?=.*[A-Za-z])(?=.*\d)[?=.*[@$!%*#?&]](A-Za-z\d@$!%*#?&){8,}$/
const { Schema } = require('json-validace')
const login = new Schema({
username: {
type: "string",
required: true,
whitespace: false
},
password: {
type: "string",
required: true,
match: /^(?=.*[A-Za-z])(?=.*\d)(?=.*[@$!%*#?&])[A-Za-z\d@$!%*#?&]{8,}$/
}
})
const result = login.validate({
username: "slickcodes",
password: "slick"
})
console.log(result)# BASH: Output
{
error: { password: { match: '"slick" does not match the regex' } },
isValid: false,
data: null
}Type: MethodDefault: no default valueWorks with: nothingUsage: validate( value ){// some sort of condition}return {isValid: false, errMessage: "custom error message"}
You can write your own validation using the validate method, the method takes in the value parsed in as a parameter and return an object containing an optional error message.
const { Schema } = require('json-validace')
const login = new Schema({
username: {
type: "string",
required: true,
whitespace: false,
validate(value) {
if (value.length > 10) {
return { isValid: true }
} else {
return { isValid: false, errMessage: "your text is too short" }
}
}
},
password: {
type: "string",
required: true
}
})
const result = login.validate({
username: "slickcodes",
password: "slick"
})
console.log(result)# BASH: Output
{
error: { username: { validate: 'your text is too short' } },
isValid: false,
data: null
}The code above checks if the value provided is hiegher than 10, since validate is a function the possiblities are basically endless. set the isValid porperty to true when if the validation is correct, and the opposite is the case if it's false however you can add an additional errMessage property which will act as a custom error message.
Modifiers allow you to make changes to the value parsed, examples of Modifiers.
- toLower
- toUpper
- default
- trim , trimLeft, trimRight
- modifyValue
- datify
Default: no default value Works with: Boolean, Strings, JWT, mongoId, Number, Floats NOTE: this will not work with arrays object and date Usage: toLower: true
the toLower is used to convert the provided text to lowercase while the toUpper transforms the provided text to uppercase. unlike the maxLength and minLength, the toLower and toUpper cannot be used together on a single key, only one can be used at a time.
const { Schema } = require("./src")
const email = new Schema({
email: {
type: "email",
required: true,
toLower: true
},
username: {
type: "string",
required: true,
toUpper: true
}
})
const result = email.validate({
email: "TEST@GMAIL.COM",
"slickcodes"
})
console.log(result)# BASH: Output
{ error: null, isValid: true, data: { email: 'test@gmail.com', username: "SLICKCODES" } }The above code show how the provided values will change.
NOTE: the change happens before any kind of validation
the default property sets a value if a value is not provided. this also means that it will not return an error even if it's required, rather it will populate the key with a value.
const { Schema } = require("./src")
const detailSchema = new Schema({
email: {
type: "email",
required: true,
toLower: true
},
username: {
type: "string",
default: "anonymous"
}
})
const result = detailSchema.validate({
email: "TEST@GMAIL.COM"
})
console.log(result)# BASH: Output
{
error: null,
isValid: true,
data: { email: 'test@gmail.com', username: 'anonymous' }
}trim is used to remove extra space around text, this works like the trim method in javascript, however this is a porperty that takes in a boolean, when it's set to true it removes the spaces and when it's set to false it ignores it. The Trim porperty by default removes space at the left and right side of a text (string) however you can also use the trimLeft, and a trimRight to specify the direction you want to trim.
const { Schema } = require('json-validace')
const login = new Schema({
username: {
type: "string",
required: true,
whitespace: false,
trim: true
},
password: {
type: "string",
required: true
}
})
const result = login.validate({
username: " slickcodes ",
password: "slick"
})
console.log(result)# BASH: Output
{
error: null,
isValid: true,
data: { username: 'slickcodes', password: 'slick' }
}Notice how the data is valid even though there was too much space, this is because the extra space where removed with trim before the whitespace check, this will be different if the space was between texts.
The modifyValue method allows you to dynamically modify a value on like other modifiers, modifyValue is a method which means you can write complex expressions and then assign a value to the key.
const { Schema } = require('json-validace')
const login = new Schema({
username: {
type: "string",
required: true,
modifyValue: (value) => value.split(' ').join('-')
},
password: {
type: "string",
required: true
}
})
const result = login.validate({
username: "slick codes",
password: "slick"
})
console.log(result)# BASH: Output
{
error: null,
isValid: true,
data: { username: 'slick-codes', password: 'slick' }
}Notice how the username changed to slick-codes even though the original entry was slickcodes? well this is the flexibility of the modifyValue method.
datify basically converts inserted date string to a javascript standard date object.
this is a relatively new modifyer and is only available in version 2.0 of the json-validace package.
const { Schema } = require('json-validace')
const userSchema = new Schema({
name: "string",
entryDate: {
type: "date",
datify: true
}
})
const result = userSchema.validate({
name: "John Doe",
entryDate: "2002-01-23"
})
console.log(result)# BASH: Output
{
error: null,
isValid: true,
data: {
name: "John Doe",
entryDate: 2002-01-25T00:00:00.000Z
}
}The func method is neigther a validator or a modifyer since it does not requires a return startment. however the func method is a very useful method that allows you write additional functionalities, this method is expected to return nothing, but it takes in a data parameter which is an object containing the value,key,isValid,error (error associated with the key), allErrors,errMessages (associated with the key) and a few others.
this is increadibly useful if you want to update the message on your browser or even console for nodejs users.
<!-- Svelte -->
<script>
</script>
<div>
</div>
<style>
</style>above is a Sveltejs scarfold, the following codes is going to be a complete form created using svelte, and of course the json-validace package.
// <script></script>
import { Schema } from "json-validace";
// hold data from the error box in the DOM
let errorMessage = {};
// the value of the input a bind to this variables
let emailValue = "";
let passwordValue = "";
// create my func function
// this method will output an error to the DOM
function outputError(data) {
errorMessage[data.key] = data.errorMessages[0] || "✔️";
}
const loginSchema = new Schema({
email: {
type: "email",
required: [true, "%key% cannot be empty!"], // assigning a custom error using porperty: [value, custom erorr]
func: outputError // attaching outputERror to func in the email param
},
password: {
type: "string",
match: [
/^(?=.*[A-Za-z])(?=.*\d)(?=.*[@$!%*#?&])[A-Za-z\d@$!%*#?&]{8,}$/,
"%key% is too weak!" // custom error message for the match property
],
func: outputError // attaching outputError to fun in the passsword param
}
});
// convert "" empty string to undefined to trigger the required erorr, since it only works when there's no value
const filterString = string => (string.trim() === "" ? undefined : string);
// Submit function
function submit() {
const result = loginSchema.validate({
email: filterString(emailValue.value), //this will triger the required error if there's no value, since required considers an empty string a value
password: filterString(passwordValue.value)
});
if (!result.isValid) return event.preventDefault();
// .. submition code here
}The code above is the javascript code and it should be within the <script></script> tag.
<!-- html -->
<!-- <div></div> -->
<div class="container">
<div class="wrapper">
<header>
<h1>Login</h1>
<p>Login to your account</p>
</header>
<!-- svelte-ignore a11y-click-events-have-key-events -->
<form action="" on:submit|preventDefault={ submit }>
<input type="text" placeholder="Email" bind:this={emailValue} />
<div class="message" class:disable={!errorMessage.password}>{errorMessage.email}</div>
<section>
<input type={ show? 'text' : 'password' } placeholder="Password" bind:this={passwordValue} />
<span class="icon" on:click={ () => show = !show}>
<Icon {show} />
</span>
</section>
<div class="message" class:disable={!errorMessage.password}>{errorMessage.password}</div>
<button>Login</button>
<a href=".">Forgotten Password?</a>
</form>
</div>
</div>/* importing font */
/* <style></style> */
@import url("https://fonts.googleapis.com/css2?family=Roboto:ital,wght@0,100;0,300;0,400;0,500;0,700;0,900;1,100;1,300;1,400;1,500;1,700;1,900&display=swap");
/* global tergetting unique to svelte */
:global(*) {
padding: 0;
margin: 0;
box-sizing: border-box;
}
.disable {
opacity: 0;
}
button:active {
background: #25074c !important;
}
a {
padding-top: 0.8em;
}
.message {
font-size: 0.77rem;
}
.container {
background-color: #360970;
height: 100vh;
width: 100%;
display: flex;
justify-content: center;
align-items: center;
font-family: "Roboto", sans-serif;
}
.container .wrapper {
background-color: white;
width: 30rem;
padding: 4rem 2rem;
border-radius: 0.5rem;
display: flex;
flex-direction: column;
gap: 0.5rem;
}
.container .wrapper header p {
color: #7c7c7c;
font-size: 0.9rem;
}
.container .wrapper form {
display: flex;
flex-direction: column;
/* gap: .5rem; */
}
.container .wrapper form section {
display: flex;
justify-content: center;
align-items: center;
position: relative;
flex-flow: column;
width: 100%;
}
form .message {
padding: 0.5em 0;
height: 1em;
padding-bottom: 2.5em;
}
.container .wrapper form section input {
width: 100%;
}
.container .wrapper form section .icon {
/* justify-self: center; */
position: sticky;
position: absolute;
right: 0;
top: 30%;
transform: translate(-0.5rem);
cursor: pointer;
}
.container .wrapper form input {
padding: 1rem;
border: 1px solid #7c7c7c;
width: 100%;
}
.container .wrapper form input:focus {
outline: 1px solid #360970;
}
.container .wrapper form button {
color: white;
background-color: #360970;
border: none;
padding: 1rem;
}
.container .wrapper form a {
color: #360970;
font-size: 0.9rem;
text-decoration: none;
}the form generated by the above code is completely validated with json-validace and it shows how useful the func method is.
you can check the output in this link: See Code Playground.
Validace provides a nested feature that allows you validate nested objects and arrays of object, this is great for complex validation.
const { Schema } = require('json-validace')
const author = {
name: {
type: "string",
required: true
},
email: "email",
hobbies: "array"
}
const bookSchema = new Schema({
name: {
type: "string",
requried: true
},
published: {
type: "date",
required: true,
},
author: {
type: "object",
required: true,
$_data: author
}
})
const result = bookSchema.validate({
name: "A Game of Thrones",
published: "1-August-1996",
author: {
name: "George R. R. Martin",
hobbies: ["books","comic books", "magazines", "trading ards", "toys"]
}
})
console.log(result)# BASH: Output
{
error: null,
isValid: true,
data: {
name: 'A Game of Thrones',
published: '1-August-1996',
author: { name: 'George R. R. Martin', hobbies: [Array] }
}
}When nesting object you need to specify that you'll be parsing in an object, once that's done you have an option to validate the object that will be parsed in or leave it. if you want to validate it you'll need to parse in the validated object inside the $_data property just like in the example above.
Arrays can also be validated if they they contain objects, once a schema has been set for an array of object every single item in the array must follow the schema and if any fails, an error will be returned.
const { Schema } = require('json-validace')
const user = {
firstName: {type: "string", required: true},
lastName: {type: "string", required: true},
surnName: "string",
username: {
type: "string",
default: "anonymous"
}
}
const userSchema = new Schema({
...user,
friends: {
type: "array",
required: true,
$_data: [user]
}
})
const result = userSchema.validate({
firstName: "Paul",
lastName: "Ezekiel-Hart",
username: "slickcodes",
friends: [{
firstName: "John",
lastName: "Doe"
},{
firstName: "Samuel",
lastName: "Jackson",
username: "sammy25"
}]
})
console.log(result)# Bash: output
{
error: null,
isValid: true,
data: {
firstName: 'Paul',
lastName: 'Ezekiel-Hart',
username: 'slickcodes',
friends: [ [Object], [Object] ]
}
}
When you're trying to validate an array of object you'll need to set the $_data property to [{}] like what we have in the example above,however if you only want to validate an array of object you can directly parse it inside of the Schema like the example below.
example
const { Schema } = require('json-validace')
// Schema
const friends = new Schema([{
firstName: {
type: "string",
required: true
},
lastName: "string"
}])
// Data
const result = friends.validate([
{ firstName: "Bob", lastName: "Samuel"},
{ firstName: "Samuel", lastName: "Jackson" },
{ firstName: "John", lastName: "Doe" },
{ firstName: "Timi", lastName: "Tams" }
])
console.log(result)Note: the example above only works for array of objects, you can validate an array of string, boolean, numbers of even floats.
# BASH: Output
{
error: null,
isValid: true,
data: [
{ firstName: 'Bob', lastName: 'Samuel' },
{ firstName: 'Samuel', lastName: 'Jackson' },
{ firstName: 'John', lastName: 'Doe' },
{ firstName: 'Timi', lastName: 'Tams' }
]
}Complex nesting is basically when multiple objects, and arrays of object get's nested within themself, this can prove useful in most cases, however it's good to note that readability will easily become an issue if you have too much nesting.
const { Schema } = require('json-validace')
// Schema
const user = new Schema([
{
name: {type:"string", required: true},
dateOfBirth: {type: "date", required: true, datify: true},
gender: {
type: "string",
toLower: true,
required: true,
enum:[ ["male", "female", "others"], "%key% is not correct!"],
},
hobbies: {
type: ["array", "%key% must be an array of hobbies"],
required: true,
maxLength: 5,
minLength: 2
},
partner: {
type: "object",
required: true,
$_data: {
name: {type: "string", required: true},
gender:{
required: true,
toLower: true,
type: "string",
// enum: [["male", "female","others"], "not a valid gender!"]
},
dateOfBirth: {type: "date", required: true, datify: true}
}
}
}
])
// Data
const result = user.validate([
{
name: "John Doe",
dateOfBirth: "1995-04-11",
gender: "Male",
hobbies: ["video game", "coding", "graphic designs"],
partner: {
name: "Stephanie",
gender: "female",
dateOfBirth: "1997-05-17"
}
},
{
name: "Samuel Jackson",
dateOfBirth: "2002-05-24",
gender: "male",
hobbies: ["football","chest", "Gambling", "suffing"],
partner: {
name: "Dominic",
gender: "male",
dateOfBirth: "2005-07-29"
}
}
])
console.log(result.data)# BASH: Output
[
{
name: 'John Doe',
dateOfBirth: 1995-04-11T00:00:00.000Z,
gender: 'male',
hobbies: [ 'video game', 'coding', 'graphic designs' ],
partner: {
name: 'Stephanie',
gender: 'female',
dateOfBirth: 1997-05-17T00:00:00.000Z
}
},
{
name: 'Samuel Jackson',
dateOfBirth: 2002-05-24T00:00:00.000Z,
gender: 'male',
hobbies: [ 'football', 'chest', 'Gambling', 'suffing' ],
partner: {
name: 'Dominic',
gender: 'male',
dateOfBirth: 2005-07-29T00:00:00.000Z
}
}
]
NOTE: You can nest object and array of object as deep as you want, however complex nesting can affect readability on the long run, so it's a good idea to keep your nesting to a minimum.
the example above is a tip of the ice burge on how complicated with schema can go, each nested object can hold another nested object and east array of object can hold another array of object, the possiblities is in a way infinity but while it is possible to create a complex nesting i strongly advice against it.
json-validace allows users to insert a custom error messages, this messages can be inserted with the validators, if inserted in the modifyer you'l not get an error, however since a modifyer does not return error, you'll also not see your error message.
To use a custom error message, you'll need to insert the it in your validator as an array, the first item of the array contains the value of the key and the second one contains the error message.
const { Schema } = require('json-validace')
const loginSchema = new Schema({
email: {
type: "email",
required: [true, "%key% is required!"],
},
password: {
type: "string",
required: [true, '%key% is required!'],
match: [
/^(?=.*[A-Za-z])(?=.*\d)[?=.*[@$!%*#?&]](A-Za-z\d@$!%*#?&){8,}$/,
"%key% not strong enough!"
]
}
})
const result = loginSchema.validate({
passowrd: "tds"
})
console.log(result)# BASH: Output
{
error: {
email: { required: 'email is required!' },
password: { match: 'password not strong enough!' }
},
isValid: false,
data: null
}like the example above, the custom error message will be inserted as the second item of the array, just like in the required, and match keys of the example above. the custom message can also be inserted in the type, and basically all validator properties with exception of the validate method.
in the example above i used the %key% to dynamically insert the key of the object.
in addition to the %key% placeholder, json-validace also provides the %value% and %property%.
- %key% : display the key of the object.
const { Schema } = require('json-validace')
const data = new Schema({
body: {
type: ["string", " (%key%) requires a string!"],
required: [true, "(%key%) is required!"],
maxLength: [20, "(%key%) is too long!"],
minLength: [5, "(%key%) is too short!"]
},
title: {
type: ["string", "%key% required a string!"],
required: [true, "(%key%) is required!"],
maxLength: [10, "(%key%) is too long"]
}
})
const result = data.validate({
body: "json-validace has alot of "
})
console.log(result)# bash: output
{
error: {
body: { maxLength: '(body) is too long!' },
title: { required: '(title) is required!' }
},
isValid: false,
data: null
}In the above output you'll notice that the %key% on the body key was populated with the (body) key.
- %value% : display the value parsed in.
The %value% placeholder, is populated with the value that is validated.
const { Schema } = require('json-validace')
const data = new Schema({
body: {
type: "string",
required:true,
maxLength: [20, "( %value% ) is too long!"],
}
})
const result = data.validate({
body: "json-validace has alot of",
})
console.log(result)# BASH: Output
{
error: { body: { maxLength: '( json-validace has alot of ) is too long!' } },
isValid: false,
data: null
}Notice how to %value% placeholder get's repopulated with "json-validace has alot of" which happens to be the exact same thing parsed into it.
- %property% : display the porperty where the error is trigered from.
The %value% placeholder, is populated with the property it is asigned to.
const { Schema } = require('json-validace')
const data = new Schema({
body: {
type: "string",
required:true,
maxLength: [20, "%key% did nt meet the %property% requirement"],
}
})
const result = data.validate({
body: "json-validace has alot of",
})
console.log(result)# BASH: Output
{
error: { body: { maxLength: 'body did nt meet the maxLength requirement' } },
isValid: false,
data: null
}