Not able to use models and routes (self-contained) in routeless engine about ember-engines HOT 3 OPEN

I think the distinction should really be made by the consuming application, when it decides whether it wants to expose the engine's route's within its own router map.

Even when it will be used as routeless, it's internal implementation may benefit significantly from using routes. They just won't alter the consuming application's URL.

The simplest example is a routeless engine that wants to having a loading template. There's no reason it can't have an ApplicationRoute with a model hook that returns a promise, which will render application.loading and then application.index.

from ember-engines.

I believe if you need routes you should be using a routable engine and not a route-less engine.

from ember-engines.

I think the distinction should really be made by the consuming application, when it decides whether it wants to expose the engine's route's within its own router map.

It's doesn't make sense when you have 2 type of engines described on RFC

The real purpose of a engine is represent a app that will be compose into a host. And we can't avoid the ability of the engine be a routable ou route-less by host app, this break the isolation and responsiblity of small app decide and increases the coupling.

The simplest example is a routeless engine that wants to having a loading template. There's no reason it can't have an ApplicationRoute with a model hook that returns a promise, which will render application.loading and then application.index.

Use routable engine for this, if you want a Loading component, use route-less with friendly interface to ember components, or an UI-addon to represent this.

Maybe we can deprecate route-less engine with arriving of Embroider that will be turn easy lazy loading components like Chat or Sidebar instead create a Engine for this.

from ember-engines.