Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Custom UI & Panels: Modules & dependencies #1157
When we switch to Polymer 3, we're no longer using HTML imports or the global scope to make functions available to other parts of the code base. Instead, we're using JS modules and functions are imported directly by the code that uses it.
I want to propose that we deprecate HTML-based custom UI and replace it with JS module custom UI. This will be easier to bundle up for users, meaning they can include their own dependencies, including Polymer.
When we release Polymer 3
2 months later
There was some confusion in the chat because we only expose Polymer on the window object. All other things (like utilities, mixins) are no longer available. This is on purpose.
We should limit the API that we expose to custom UI such that the frontend can evolve without breaking the expectations of custom UI.
Our API to custom UI should be:
Custom UI can use any framework they want. They are not limited to Polymer. In fact, the Polymer team is actively suggesting to no longer use Polymer templates. Instead, they suggest you use their new Lit Element (source)