Re: [webcomponents] Support renaming, aliasing, or namespacing imported elements (#344)

@domenic for @philipwalton's second example, where an app uses two custom elements that both require different, but of the same name, components - would the constructor proposal above resolve that? Am I right in thinking it would then require a component author to take components as parameters in their constructors, a la dependency injection?

Is there also the possibility of simply using unique registries? Or more simply I guess on a unique document, rather than the global document. In which case an author could register the elements they depend on in their own document, and export their resulting component as a class.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/344#issuecomment-166758887