Mailspring/spec-nylas/fixtures/packages/package-with-models/main-module.coffee

Model = require '../../../../src/flux/models/model'
Task = require '../../../../src/task'

class ModelA extends Model
class ModelB extends Model
class TaskA extends Task

module.exports =
  modelConstructors: [ModelA, ModelB]
  taskConstructors: [TaskA]
  activate: ->
refactor(models): Enables 3rd party plugins to add Models & Tasks Summary: Adding serialzable registry Added DatabaseObjectRegistry rename modelReviver to deserializeObject Consolidate deserizlie Get rid of model methods from Utils DatabaseRegistry change notifications Logic to throttle database refresh requests Fixes in nylas-exports Silent model setup Continue to resolving the database setup phase for non main windows. A packages `activate` method does not actually get called until the DatabaseStore says that it's ready. This is necessary to ensure that a package that introduces database changes has those schema changes take hold before the activate happens. However, in windows like the `onboarding` window that do not depend on a database at all, there is no setup that is run and the promise use to never resolve thereby making the packages never activate. In this case, any external windows will go ahead and let their packages activate. Check subclass instead of instance! Use the correct types for "messages" and "drafts" Move Salesforce models Proper references to Model and Attributes Convert Salesforce stores to NylasStores and fix paths Move database setup to DB Test Plan: todo Reviewers: bengotow Reviewed By: bengotow Differential Revision: https://phab.nylas.com/D1899 2015-08-20 07:25:56 +08:00			`Model = require '../../../../src/flux/models/model'`
			`Task = require '../../../../src/task'`

			`class ModelA extends Model`
			`class ModelB extends Model`
			`class TaskA extends Task`

			`module.exports =`
			`modelConstructors: [ModelA, ModelB]`
			`taskConstructors: [TaskA]`
			`activate: ->`