Browser Model

[DylanPiercey]

Although 90% of "model.js" doesn't make sense in the browser I think implementing it with some basic features (like creating a schema from an object and storing the model name) would be handy to make the following code easier to be isomorphic.

var Test = mongoose.model('test', {
  name: { type: String },
  test: { type: String },
});

// Browser should have
Test.schema
Test.modelName

Currently I have to separate out that schema if I want to use it in the browser, also I have to explicitly pass around the modelName since schema's don't have names.

Thoughts?

[mkastner]

I've run into the same problem. Maybe this abstracted shared schema module could work for you (with CommonJS):

// schema-def.js
// abstracts the schema definition from the schema object creation

var schemaDef = {
    test: {
        name: { type: String },
        test: { type: String }
    }
}

module.exports = schemaDef;

Now you can require the abstracted schema definition from client and server side like this:

// client-models.js
// sharing same schema defintion with server

var schemaDef = require('schema-def.js');

var Test = mongoose.model('test', schemaDef.test);

// of course no plugins and other fancy server stuff

// server-models.js
// sharing same schema defintion with client

var schemaDef = require('schema-def.js');

var Test = mongoose.model('test', schemaDef.test);

// Since the schema definition is abstracted,
// on the server side you can add your plugins, indexes etc. 

My thoughts.

[vkarpov15]

I like this idea. Hasn't really been a high priority since getting documents and schemas to work in the browser was already quite an odyssey