Remove metadata from modules

Since the upcoming concept of having a context provider, the return value that used to set meta information about the module seems to obsolete.

Or is there still a use case for it?

export default (options = {}) => {
  return (module) => {

    // Return some META information about the module
    return {}
  }
}

[christianalfoni]

I see now 😃

So something like:

controller.extendModules({
  newMethod() {}
})

And all module instantiations now has access to a new method:

module => {
  module.newMethod()
}

[garth]

I have been giving this issue some thought for a while and for my current project I didn’t want to depend on .meta. Meta is not explicit, cannot be validated at the time it’s created and may clash with other modules.

Instead I propose that we try something similar to context, but for modules… when a module is defined it is given module on which we can add[stuff]() I would like to be able to add my own methods to the module param in the same was as we do with signal context. This would allow us to do away with returning the ambiguous meta and enable more explicit features to be added to modules with better control.