Hey, is it possible to add support for allowBlank so that not only '', but null also counts as blank? The use case is that I have

  email: {
    allowBlank: true,
    default: '', // want it to default to null
    type: mongoose.SchemaTypes.Email,
    unique: true,
  },

and the problem is that 2 emails with '' as values don't pass the unique validation. Having those as nulls will make the uniqueness validation pass.

Seems that the fix would be checking val not only for '', but for null on this line https://github.com/konsumer/mongoose-type-email/blob/master/index.js#L7

test6@12
If I just pass this it accepts email. Even though it doesn't have any subdomain like i.e. .com, .co.in etc.. please let me if you are planning to fix this. But it works perfectly.

The devDependency mongoose was updated from 5.2.17 to 5.2.18.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency mongoose was updated from 5.5.10 to 5.5.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 5.2.0 of mocha was just published.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I having get this error: _UserModel validation failed: email: this.constructor.checkRequired is not a function

this is my schema:

const mongoose = require('../db');
require('mongoose-type-email');

const userSchema = new mongoose.Schema({
  name: {
    type: String,
    required: true
  },
  email: {
    type: mongoose.SchemaTypes.Email,
    required: true,
    index: {
      unique: true
    }
  },
  password: {
    type: String,
    required: true
  },
  phoneNumber: String
});

module.exports = mongoose.model('UserModel', userSchema);

Since 1.0.11 validation of an invalid email brings up a required error instead of invalid email address when used together with required: true.

While working with this package, I noticed that the email validation regex allows for something like 'email@email' to pass.
Doing a little searching I found this regex string catches pretty well, may want to consider using it instead.

(?:[a-z0-9!#$%&'+/=?^_{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_{|}~-]+)|"(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21\x23-\x5b\x5d-\x7f]|\[\x01-\x09\x0b\x0c\x0e-\x7f])")@(?:(?:a-z0-9?.)+a-z0-9?|[(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?).){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?|[a-z0-9-][a-z0-9]:(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21-\x5a\x53-\x7f]|\[\x01-\x09\x0b\x0c\x0e-\x7f])+)])

The devDependency mockingoose was updated from 2.12.0 to 2.13.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mockingoose is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency release-it was updated from 8.3.1 to 8.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

release-it is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 7.4.4 of release-it was just published.

This version is covered by your current version range and after updating it in your project the build failed.

release-it is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This is to avoid this
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/cryptiles. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

yarn add mongoose-type-email
yarn add v1.17.3
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/mongoose-type-email: getaddrinfo EAI_AGAIN registry.yarnpkg.com registry.yarnpkg.com:443".
info If you think this is a bug, please open a bug report with the information provided in "/usr/src/app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Hi,
Following 2bd35bb and its origin issue #24, there might be some change of behavior in the way error message are defined.

Considering this schema:

const userSchema = mongoose.Schema({
	email: {
		type: mongoose.SchemaTypes.Email,
		required: [true, "error.common.required"],
		unique: true,
		message: "error.common.email",
	},
});

If an email is invalid for example foobar i'm expecting to get error.common.email as error message but i get error.common.required.
This is due to the fact that checkRequired does not only check for the mandatory value but also for the email validation:

Current code for checkRequired is :

mongoose.SchemaTypes.Email.prototype.checkRequired = function (val) {
	return typeof val === 'string' && validateEmail(val, this.options);
};

My current alternative is to override this function by setting back the default mongoose behavior:

mongoose.SchemaTypes.Email.prototype.checkRequired = function (val) {
	return val != null;
};

That way, requirement is handled as before and will throw error.common.required only if value is missing. In case of incorrect email, checkRequired will be true, passing the requirement validation and will fail later in the plugin lifecycle providing error.common.email error as expected.

Beware that my alternative only care about non null value for requirement. It might be interesting to take care of allowBlank options here as well.

Found this little error. I guess you have to update this line: https://github.com/konsumer/mongoose-type-email/blob/master/package.json#L32

[23:13:53] sobolev :: MacBook-Pro-Nikita ➜ Documents/Frontends/razgrebaem ‹master*› » npm list mongoose
[email protected] /Users/sobolev/Documents/Frontends/razgrebaem
└── UNMET PEER DEPENDENCY [email protected]

npm ERR! peer dep missing: mongoose@, required by [email protected]
npm ERR! peer dep missing: mongoose@, required by [email protected]
npm ERR! code 1

Hey, nice plugin!
However, I am having an issue with allowBlank when field's required is set to a function.

To reproduce have this schema:

require('mongoose-type-email')
const { Schema } = mongoose

const userSchema = new Schema({
  email: {
    allowBlank: true,
    default: '',
    required: function() {
      return false // returning false here for the sake of the display
    },
    type: mongoose.SchemaTypes.Email,
  }
})

Most likely this is happening because on this line https://github.com/konsumer/mongoose-type-email/blob/master/index.js#L6 it doesn't check if the required is a functon and that it doesn't return false.

The devDependency mongoose was updated from 5.3.16 to 5.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mongoose is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴