Registering controllers to modules instead of global scope

[remojansen]

Imported from inversify/inversify-express-utils#201

I've noticed that controllers are automatically registered to global scope when they are imported. A cleaner way would be to allow each package to export its controllers and then load them into the required container, as with any other dependencies.

Is there a way to do so now or would I need to implement this feature?

-- @shlomokraus

Also looking at this. Spent a good bit of time scratching my head because I'm pulling in multiple Express apps into a single server and then routing across them by hostname, and the behavior was not what I expected.
-- @eropple

[remojansen]

@shlomokraus @eropple I think this is a good idea. We need to come up with a proposal for potential changes in the API and once we all agree we will be able to implement it. PRs are welcome so if you guys would like to contribute we should be able to help and guide you.

[shlomokraus]

@remojansen Why is that relevant for the main repo?
I thought this is a behavior of the express-utils project.

[shlomokraus]

@remojansen
As in this line:
https://github.com/inversify/inversify-express-utils/blob/206a8b1b541c4abdaf49cf20d65855e9abef5f14/src/decorators.ts#L20