I encountered a situation (once again) where I'm wiring something else than a view with wireView since I need it to be injected as a class instead of an instance. In this case a model in a collection.
The collection handles instantiation, but I need the models to receive dependency injections. It's a bit of a rare case, since normally my models don't have any dependencies, but this is an aggregate model, i.e. it manages a number of other models (and collections)
@geekdave I think the easiest will be to provide an alias, something like wireFactory? If at some point in time we need to differentiate between wireFactory and wireView that won't be a problem.
I encountered a situation (once again) where I'm wiring something else than a view with
wireViewsince I need it to be injected as a class instead of an instance. In this case a model in a collection.The collection handles instantiation, but I need the models to receive dependency injections. It's a bit of a rare case, since normally my models don't have any dependencies, but this is an aggregate model, i.e. it manages a number of other models (and collections)
@geekdave I think the easiest will be to provide an alias, something like
wireFactory? If at some point in time we need to differentiate betweenwireFactoryandwireViewthat won't be a problem.