Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
@peacechen/nexus-validate
Advanced tools
Add extra validation to GraphQL Nexus in an easy and expressive way.
const UserMutation = extendType({
type: 'Mutation',
definition(t) {
t.field('createUser', {
type: 'User',
// add arguments
args: {
email: stringArg(),
age: intArg(),
},
// add the extra validation
validate: ({ string, number }) => ({
email: string().email(),
age: number().moreThan(18).integer(),
}),
});
},
});
# npm
npm i @peacechen/nexus-validate yup
# yarn
yarn add @peacechen/nexus-validate yup
nexus-validate
usesyup
under the hood so you need to install that too.nexus
andgraphql
are also required, but if you are using Nexus then both of those should already be installed.
Once installed you need to add the plugin to your nexus schema configuration:
import { makeSchema } from 'nexus';
import { validatePlugin } from '@peacechen/nexus-validate';
const schema = makeSchema({
...
plugins: [
...
validatePlugin(),
],
});
The validate
method can be added to any field with args
:
const UserMutation = extendType({
type: 'Mutation',
definition(t) {
t.field('createUser', {
type: 'User',
args: {
email: stringArg(),
},
validate: ({ string }) => ({
// validate that email is an actual email
email: string().email(),
}),
});
},
});
Trying to call the above with an invalid email will result in the following error:
{
"errors": [
{
"message": "email must be a valid email",
"extensions": {
"invalidArgs": ["email"],
"code": "BAD_USER_INPUT"
}
...
}
]
}
If you don't want to use the built-in validation rules, you can roll your own by throwing an error if an argument is invalid, and returning void if everything is OK.
import { UserInputError } from '@peacechen/nexus-validate';
t.field('createUser', {
type: 'User',
args: {
email: stringArg(),
},
// use args and context to check if email is valid
validate(_, args, context) {
if (args.email !== context.user.email) {
throw new UserInputError('not your email', {
invalidArgs: ['email'],
});
}
},
});
The plugin provides a formatError
option where you can format the error however you'd like:
import { UserInputError } from 'apollo-server';
import { validatePlugin, ValidationError } from '@peacechen/nexus-validate';
const schema = makeSchema({
...
plugins: [
...
validatePlugin({
formatError: ({ error }) => {
if (error instanceof ValidationError) {
// convert error to UserInputError from apollo-server
return new UserInputError(error.message, {
invalidArgs: [error.path],
});
}
return error;
},
}),
],
});
If you want to change the error message for the validation rules, that's usually possible by passing a message to the rule:
validate: ({ string }) => ({
email: string()
.email('must be a valid email address')
.required('email is required'),
});
validate(rules: ValidationRules, args: Args, ctx: Context) => Promise<Schema | boolean>
Type | Docs | Example |
---|---|---|
string | docs | string().email().max(20).required() |
number | docs | number().moreThan(18).number() |
boolean | docs | boolean() |
date | docs | date().min('2000-01-01').max(new Date()) |
object | docs | object({ name: string() }) |
array | docs | array.min(5).of(string()) |
The Args
argument will return whatever you passed in to args
in your field definition:
t.field('createUser', {
type: 'User',
args: {
email: stringArg(),
age: numberArg(),
},
// email and age will be typed as a string and a number
validate: (_, { email, age }) => {}
}
Context
is your GraphQL context, which can give you access to things like the current user or your data sources. This will let you validation rules based on the context of your API.
t.field('createUser', {
type: 'User',
args: {
email: stringArg(),
},
validate: async (_, { email }, { prisma }) => {
const count = await prisma.user.count({ where: { email } });
if (count > 1) {
throw new Error('email already taken');
}
},
});
nexus-validate is provided under the MIT License. See LICENSE for details.
This library is based off of @joosepalviste/nexus-validate which was forked from nexus-validate . The latter appears to be abandoned. The hope is that this will be a community-supported version. Maintainers are welcome.
FAQs
Validation plugin for Nexus JS.
We found that @peacechen/nexus-validate demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.