Adding models to a parent engine's `store`.

So let’s say you’re in child-engine with this dependency chain:

dependencies: {
  services: [
    'store'
  ]
}

The store that is passed in is effectively in parent-engine’s scope. If child-engine wishes to extend parent-engine’s store with additional available models that is presently only possible by abusing the app folder inside of child-engine.

We need to define a pattern for this behavior as it is almost guaranteed to be an issue.

/cc @kaceykaso @jwlawrence @cklimkowsky @trentmwillis

[buschtoens]

What a coincidence that I also just ran into this issue. 😄

I’d just like to add that besides models we’d also need support for adapters & serializers. It would be pretty neat if I could define an application (or engine) adapter that would work just like the traditional application adapter, but scoped / limited to the models provided by the engine.

[mvrkljan]

@villander any chance you could point to a ticket in ember data repo where the related issue can be tracked? Thank you!