Align the mount and route APIs

[jsturgis]

This RFC describes the motivation and implementation for aligning the mount and route API signatures.

https://github.com/emberjs/ember.js/pull/19402

[meirish]

This may be out of scope, but it feels related to https://github.com/ember-engines/ember-engines/issues/80 (though I realize the inside-out nature of this adds complexity).

[wagenet]

Is there still interest to move this forward?

[villander]

IMO we should discuss and see if it's still relevant and have some chance to be included on https://github.com/emberjs/rfcs/pull/819

cc/ @runspired @SergeAstapov

[ef4]

This RFC is probably not aligned with what we want to do. It's motivation says:

Some Ember applications utilize in-repo ember-engines strictly for their lazy loading and code organization features and not for their isolation features.

Going forward, these are not relevant reasons to use engines, because we have better alternatives for both lazy loading and code organization.

• for lazy loading, you can use import() via either ember-auto-import or embroider
• for code organization, first-class component templates means you can use all the organization patterns that work with normal ES modules.

[achambers]

@SergeAstapov / @void-mAlex Do you have any thoughts on this?

[SergeAstapov]

@achambers I strongly agree with what Ed said in previous comment and I'm not sure I see the actual problem this gonna solve as Engines by design are separate apps and they should not leak anything up to the host app.

[wagenet]

Given the fact that this is not aligned with our current direction we are moving to FCP to Close.

[achambers]

Looks like no comments so this should be good to close. Will leave to the RFC #2 meeting to do so.