How to replace mixins for large controllers or routes

Hi,

I know that mixins are not recommended any more, but I find them especially useful for breaking up large sections of code for the same controller or route. For example a section that deals with billing is all put inside one mixin and another section that deals with settings is all put inside another mixin. I find this a great way to logically separate a controller that may otherwise turn too big to read/understand/edit later.

Is there a way to have the same “convenience” but without prompting errors by Ember?

Thanks Image may be NSFW.
Clik here to view.

1 post - 1 participant

Read full topic