You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was a failed attempt at allowing models to declare a dependency. As of 2.0 this dependency is more explicit (see PersistedModel). This change will require similarly explicit dependency for Email, Push and similar models.
Before we can remove autoAttach, we need to implement a mechanism for attaching an existing model to a datasource via models.json without creating a subclass - see loopbackio/loopback-datasource-juggler#119.
FWIW, loopback-boot 2.0 split the boot in two phases: model definition (models/*.json) and model configuration (models.json). It is possible to configure any model in models.json file as long as it can be found via loopback.getModel(name), which is true for built-in models.
Activity
bajtos commentedon May 30, 2014
Before we can remove
autoAttach, we need to implement a mechanism for attaching an existing model to a datasource viamodels.jsonwithout creating a subclass - see loopbackio/loopback-datasource-juggler#119.bajtos commentedon Jul 8, 2014
FWIW, loopback-boot 2.0 split the boot in two phases: model definition (
models/*.json) and model configuration (models.json). It is possible to configure any model inmodels.jsonfile as long as it can be found vialoopback.getModel(name), which is true for built-in models.bajtos commentedon Jul 22, 2014
This can be done in a way that would allow people to use
loopback-boot@1.xtogether withloopback@2.x.bajtos commentedon Oct 3, 2014
The current status:
loopback-boot@1.xcomes with it's own implementation ofautoAttach, thus the method can be safely dropped from loopbackmodels.json, that's already supported inloopback-boot@2.x.Conclusion: the only remaining blocker is that we need a next major version of loopback.