Usage without mixins

When using ES Classes and/or TypeScript, it is not the best approach to use mixins. I know is possible, using class XYZ extends Component.extend(Mixin) { ... but it would be nice to not have an alternative to using mixins.

[mike-north]

Looking at the mixins in question, it doesn’t seem all that difficult for those who want a more explicit “composition instead of inheritance” option.

Example:

https://github.com/bgentry/ember-apollo-client/blob/5296032ff0b10ac3bd9bebf6cca8f56946c90929/addon/mixins/route-query-manager.js#L5-L8

99% of the complexity in this addon lives on the service, which is excellent. It’s very much true that a Router/Component/Object has an object that provides apollo support rather than being an object that includes apollo support.

If you don’t want to use the RouteQueryManager mixin, just inject the service:apollo yourself, and add the appropriate one-liners to your route (or a route base class).

For a first-class TS/ES6 approach, looks like the work would be:

• document the mixin-free approach – effectively doing what the respective mixins do
• add a few acceptance tests (A route, component and object) to protect against regression. The main thing that could go wrong in the future is ordering setup/teardown of the apollo client w/ the rest of the setup/teardown logic. As it stands, I doubt it matters if you do the apollo work before or after this._super(...arguments); but that could change. Tests would alert us to that change.

[tchak]

I implemented queryManager macro on my fork if some of you are interested in trying it out and give feedback. cc @buschtoens

https://github.com/tchak/ember-apollo-client/tree/drop-mixins