module-level context

[vbelolapotkov]

As per spec modules are not allowed to update application context. So module heavily depends on context. At least it uses context to connect actions and containers together.

On the other hand context is the app specific thing and may not contain all objects used by module. So to reuse modules we have to preconfigure context for each module. And this can lead us to conflicts when the same context name required by different modules for different purposes.

To break this dependency It would be great to have the option to store in the "module context" value returned by load function.
This will eliminate the issue with naming conflicts and there will be no need to preconfigure app context for module.

I'd do this only for module specific storage/objects but not for meteor packages as it seems to be ok to have them in context.

Any thoughts on this?

[TeemoWan]

+1