Dependencies between nested engines

Hello,

Can you please help me to describe dependencies for following structure?

Host Application ->
   service:ajax
   Nested 1 (async routable) ->
     service:socket
     Nested 1.1 (async routable)
       -> how to pass socket service via dependencies from 1 to 1.1 ?
     Nested 1.2 
   Nested 2 (async)

In host app I could write something like this in app.js, but the trouble is that socket service is not available until I load it.

Nested1.1: {
    dependencies: {
      services: ['ajax', 'socket']
    }
  }

I tried to write it in Nested1 engine.js file, but it seems Nested1.1 is looking for dependencies in Host app and not in parent engine ? service:socket is quite big and I wouldn’t want to move it on Host level.

If this make sense routes in Nested 1 described like this

export default buildRoutes(function() {
  this.route('participant', { path: '/:id' }, function() {
    this.route('index', { path: '/' }, function() {
      this.mount('viewer');  // This is Nested 1.1 mount
    });
  });  
});

I finally shared socket as a property of the global app service, but do not think it’s good.

Thank you.

[lvegerano]

I’m running into this issue as well but with externalRoutes dependencies. I have an engine that I mount to the host app and also to another engine that is mounted to the same host app.

Host App
    mounts: Engine A
    mounts: Engine B
        mounts: Engine A

Engine A deps:
   externalRoutes: {
        'route-dep': 'host.app.route',
    }

Engine B deps
   Engine A deps
       externalRoutes: {
           'route-dep': 'engine.b.route'
       }

But when Engine A tries to route to route-dep from Engine B, instead of routing to engine.b.route it routes to host.app.route Is there a way around this?

[swarnavallis]

@swarnavallis and this is exactly what I asked but didn’t find any practical solution without sharing via host app.

So is there any possibility that this will be addressed in near future? @catz @stefanpenner