Closed rslawik closed 3 years ago
@rslawik Looks like this was done in 4.0.0
?
Only the first step (switching to LitElement) base class is done in 4.0.0.
The second one (unifying the lifecycles) is not complete yet. There are some opportunities for optimisations in LitElement. For example:
data
triggers 2 renders (one for the input, one for the internal property). Can this be reduced to 1?updateComplete
promise be synchronised with the 'google-chart-ready'
event?I'd keep this issue open until I check if those can be implemented without breaking changes.
Closing. This can be revisited when migrating to next version of LitElement.
LitElement is a base class for creating lightweight web components. It is the next generation after Polymer 3.
This component does not use some of the Polymer features (like data bindings), so switching to LitElement will reduce the footprint of this component. The API can stay backwards compatible.
LitElement introduces asynchronous rendering which fits well with Google Charts rendering (i.e. waiting for
'ready'
event). This migration should ideally happen in two steps: