decouple from ember-cli about blprnt HOT 4 OPEN

@trabus maybe we can do a minimal thing, that sufficiently decouples this case. We can see how it feels, then grow it to something more fully fledged? Call the effort "structures", and aim for that to be the guiding light?

You have likely thought about this more then me, so you likely have much more context.

from blprnt.

Regarding references to pod, did you have any strategies in mind to abstract this yet? I was thinking maybe something like the concept I had for structures, but simpler?

from blprnt.

Regarding references to pod, did you have any strategies in mind to abstract this yet? I was thinking maybe something like the concept I had for structures, but simpler?

I believe the concept of structures, may enable this.

from blprnt.

The only thing gives me pause is that they kind of need to know about the resolver, but we don't want to couple that with the implementation.
Maybe structures can be flexible enough that the resolver (or any thing like that dealing with the generated product) can just be optionally considered from inside any specific structure implentation, rather than coupling the concept.

from blprnt.