Kenneth Rohde Christiansen

the SW fetch event seems to consult all caches. It might be that a new one isnt consulted but then I would need to update the SW. Maybe it is...

Sure why not, how would this look?

I tried doing mixins.... but doing a JS mixin from TypeScript is apparently impossible... spent quite some time on this and found out that a lot of clever people had...

Why not just check if this.shadowRoot exists? You also shouldn't need this._root. I don't really see a problem with creating the root at this point as it should be a...

This is not needed if my PR gets merged in lit-html https://github.com/PolymerLabs/lit-html/pull/239

So any update on this? :)

The point is to stay close to the platform as possible, which means aligning with what is going on with standards etc. Web components already supports events via EventTarget and...

@filipbech just did a router implementation. I haven't thought a lot about that myself, as I normally just do a custom one for my projects. I also think a lot...

The following works :-) ``` async connectedCallback() { await super.connectedCallback(); this.favorite = this.product.isfavorite; } ``` But I am wondering whether we should just render immediately when connected. What is your...

That is exactly what it does today. It returns a promise which resolves :-) You could also do ``` connectedCallback() { super.connectedCallback().then(_ => { this.favorite = this.product.isfavorite; }); ``` But...