Ideas for v3.0

[bajtos]

Copy of comment by @raymondfeng:

1. I think we need to organize the boot into multiple phases, such as:
   • discover/load: Find and load configurations
   • resolve/wire: Resolve the references (such as model.dataSource) and wire them together
   • startup: Initialize the datasources/models (model class can potentially have lifecycle event listeners)
   • shutdown: Emit events to notify model classes of system shutdown
   • refresh/update: React to config changes, especially additions
2. How do we load plugin modules, for example, loopback-passport, loopback-push-notification which typically has dependencies to app and also contributes middlewares/models/datasources? See https://github.com/strongloop/loopback-example-component/issues/4
3. Do we want to support both sync and async booting? Or eager/lazy booting? See Add support async scripts #50 for implementation of async boot scripts.

[Coobaha]

you should add support for custom coffeescript model files, in common/models
like customer.json and customer.coffee
in compiler.js .coffee is mentioned, but this file extension is not supported.

[offlinehacker]

Also support for having multiple model JavaScript files for same model in multiple folders, and all of which getting run at boot, so you could separate some logic for client and server.

[bajtos]

Also support for having multiple model JavaScript files for same model in multiple folders, and all of which getting run at boot, so you could separate some logic for client and server.

You should be able to create client-only and server-only models by extending the shared model:

common/models/product.json
{
  "name": "ProductBase",
  // properties, relations, etc.
}

common/models/product.js
// shared code

server/product.json
{
  "name": "Product",
  "base" : "ProductBase"
}

server/models/product.js 
// server-only code

[bitmage]

@Coobaha I've submitted a pull request for this:

#55

[bajtos]

@offlinehacker Also support for having multiple model JavaScript files for same model in multiple folders, and all of which getting run at boot, so you could separate some logic for client and server.

See this discussion in LoopBack: strongloop/loopback#397

[bajtos]

How do we load plugin modules, for example, loopback-passport, loopback-push-notification which typically has dependencies to app and also contributes middlewares/models/datasources?

We have discussed the component architecture here: https://github.com/strongloop/loopback-example-component/issues/4

Do we want to support both sync and async booting?

#50 implemented support for async boot scripts.