U have a schema where the user has an array of emails. I want to validate that each of these items are valid/invalid. But there are not getting validated. Please see the mocha,should test code here:

require.paths.unshift('./node_modules');
require('should');
var assert = require('assert');

var mongoose = require('mongoose')
, Schema = mongoose.Schema
, mongooseTypes = require("mongoose-types")
, db = mongoose.createConnection(getMongoUrl());

mongooseTypes.loadTypes(mongoose);

var Email = mongoose.SchemaTypes.Email;

/* if we use the below code.. we get: CALL_NON_FUNCTION_AS_CONSTRUCTOR exception

var emailType = mongoose.SchemaTypes.Email;
var Email = new mongoose.Schema({
type: emailType,
unique: true,
required: true,
lowercase: true
});

*/

describe('Schema with just one email; Simple User with an invalid email', function(){
var UserSchema = new Schema({
email: Email
});
var User = db.model('User', UserSchema);
//User.remove({}, function (err) {});

describe('Save invalid email', function(){
it('should throw vaidation error', function(done){
var user = new User({email: 'asdf.com'});
user.save(function(err){
err.message.should.equal('Validation failed');
done();
});
})
})
});

describe('Schema with an ARRAY of emails; User with 1 or more invalid emails', function(){
var UserSchema2 = new Schema({
emails: [Email]
});
var User2 = db.model('User2', UserSchema2);

describe('Save invalid email', function(){
it('should throw vaidation error', function(done){
var user2 = new User2({emails: ["rrr"]});
user2.save(function(err){
console.log(err);
assert.exist(err);
assert.exist(err.message);
assert.equal(err.message, 'Validation failed');
done();
});
})
})
});

function getMongoUrl() {
if (process.env.VCAP_SERVICES) {
var env = JSON.parse(process.env.VCAP_SERVICES);
var obj = env['mongodb-1.8'][0]['credentials'];
}
else {
var obj = {
"hostname": "localhost",
"port": 27017,
"username": "",
"password": "",
"name": "",
"db": ""
}
}
obj.hostname = (obj.hostname || 'localhost');
obj.port = (obj.port || 27017);
obj.db = (obj.db || 'test');

if (obj.username && obj.password) {
    return "mongodb://" + obj.username + ":" + obj.password + "@" + obj.hostname + ":" + obj.port + "/" + obj.db;
} else {
    return "mongodb://" + obj.hostname + ":" + obj.port + "/" + obj.db;
}

}

//to run.. mocha <testfile.js>

emails in the form [email protected] where ID is [a-z0-9]+ throw an "email is invalid" error for the Email validator

Hi,

Thanks for writing this great plugin. I'm using it in several collections.

I'm also trying to use mongoose-types in a embedded document, but it does not work: The first sub-document is added without any problems but then I cannot add more sub-documents. I always get the following error:

http.js:543
throw new Error("Can't use mutable header APIs after sent.");

Here is the code:

//add tracker to account.

var Actor = mongoose.model('Actor');
function add_tracker(req, res, next) { 
    Actor.findById(req.params.id, function(err, actor) {
        if (err) {
            console.log(err);
        }
        var tracker_value = req.body.tracker.value;
        var tracker = { value: tracker_value };
        var trackers_size = actor.trackers.length;
        actor.trackers.push(tracker);
        actor.save(function(err){
            res.local("actor", actor);
            if (err) res.send({ error: err.message });
            var tracker = actor.trackers[trackers_size];
            res.partial('account/_tracker', { object: tracker }, function(err, html) {
              if (err) {
                  res.send({ error: err.message });
              } else {
                  res.send({ prepend: html, to: '#tracker_list' });
              }
            });
          })
    });
}

//database schema:

var mongoose = require('mongoose'), 
    mongooseTypes = require("mongoose-types"),
    useTimestamps = mongooseTypes.useTimestamps;

var Trackers = new Schema({
        value : String
 });
Trackers.plugin(useTimestamps);

var Actor = new Schema({
        , name     : String
        , trackers      : [Trackers]
});
mongoose.model('Actor', Actor);

If I remove mongoose-types from the embedded the error does not occur.

Thanks.
Best regards,
Migrate

Seems neglected with 15 PR waiting?

Might want to look at http://bassistance.de/jquery-plugins/jquery-plugin-validation/ for a more comprehensive email regex. More specifically here: http://ajax.aspnetcdn.com/ajax/jquery.validate/1.8/jquery.validate.js search for "email:"

I can't access createdAt. I can access and also see updatedAt when querying and looking at the collection
(I guess that createdAt uses the date in ObjectId and that's why I don't see it toghether with updatedAt in my collection?).

These are the packages I use:
[email protected]
[email protected]
[email protected]

Hi,
Currently mongoose is on release 0.0.5, but types are dependent on 1.0.0 and registered in npm registry. How can we use this ?

The stuff to the left the @ should have its case preserved.

http://email.about.com/od/emailbehindthescenes/f/email_case_sens.htm

Though there are a huge diversity and far too many redundant sources, the schema types are fairly well defined and some entities (standards orgs) present profiles that are generally accurate. Something that would import or retain all general schema types based on the rigid foreign definition and the various validation requirements, or are there tools already that fetch the remote definitions and translate to the necessary structure?

The URL validation appending a ? in the end of url.

The url regex checks for ftp, http,https, however there are a lot more protocols out there, so it would be best to check for word only (2 or more chars). For example, chrome uses: chrome:/ which is used as the return url when doing the oauth2 dance from within a plugin.

The e-mail type ignores a "required:false" Schema attribute.

from the tests it seems that the URL normalisation removes the 'www.' from the beginning of the URL. A lot of websites will not work withut the www. prefix (primarily websites that aren't configured correctly but there are still a lot of them out there. Can the URL normalisation be turned off?

.

Tried using mongoose-types for URL matching, but it's butchering my URLs. Not particularly liking the edits it's doing. It keeps removing the port number and adding question marks to the end of every URL. >.>

Turns out, I can't use remove() on an embedded document without mongo complaining when I try to save the parent document. :(

the email regex used doesnt allow for +'s in emails. This is still acceptable in an email address before the @ character