codecombat/server/analytics/AnalyticsUsersActive.coffee

mongoose = require 'mongoose'
plugins = require '../plugins/plugins'

AnalyticsUsersActiveSchema = new mongoose.Schema({
  created:
    type: Date
    'default': Date.now
}, {strict: false})

module.exports = AnalyticsUsersActive = mongoose.model('analytics.users.active', AnalyticsUsersActiveSchema)
Capture active user metrics Watching for these events: Level completed User registered Playtime of 30s in a level Purchase Payment Subscribe Earned an achievement 2014-12-04 15:57:57 -05:00			`mongoose = require 'mongoose'`
			`plugins = require '../plugins/plugins'`

			`AnalyticsUsersActiveSchema = new mongoose.Schema({`
			`created:`
			`type: Date`
			`'default': Date.now`
Revert "Fixed #1076, and all other instances of empty objects being stripped out of documents. Turns out mongoose was doing this intentionally as a feature? I don't understand why that's on by default. Oh mongoose." Saw that this caused 500s on /auth/whoami with no cookies set, with this error: debug: 500: MongoError: E11000 duplicate key error index: coco.users.$emailLower_1 dup key: { : null } Probably we need to be much more careful about what changes this blanket change to the minimize Mongoose option might introduce, since tests didn't catch this, but it would have taken the site down for anyone not logged in already. This reverts commit 121f07d020847f313698a8c077220fdfc6ad0ae8. 2015-01-09 21:30:05 -05:00			`}, {strict: false})`
Capture active user metrics Watching for these events: Level completed User registered Playtime of 30s in a level Purchase Payment Subscribe Earned an achievement 2014-12-04 15:57:57 -05:00
			`module.exports = AnalyticsUsersActive = mongoose.model('analytics.users.active', AnalyticsUsersActiveSchema)`