Re: [w3c/webcomponents] [Template Instantiation] Layering and additional use cases (#747)

@annevk thanks for the feedback!

> `NodePart`

This was a lazy abbreviation on my part. I intended to refer to a `NodeTemplatePart`. I will fix this in the original issue text.

> One thing I'm missing above is attributes

As stated above, the intent here is to be additive to the original proposal. So, `AttributeTemplatePart` and `InnerTemplatePart` still apply at Level 1. Is there an attribute use case missing from the original proposal that you would like to see mentioned here?

> `cloneWithParts()`

We don't have a rigid opinion here, and I can only speculate about what the best approach should look like given various hypothetical spec/implementation constraints.

> Frameworks

Speaking on behalf of the Polymer team, we have experimentally confirmed that these features could satisfy the use cases of the Polymer and lit-html libraries.

I have an on-going dialogue with Angular related to the Template Instantiation proposal. Some of the use cases described above came out of direct feedback from their team. I referred Angular to this issue shortly after it was filed, and I am hopeful that they will offer updated feedback soon.

I would appreciate hearing from Ember as well. I understand they may have met the initial proposal with some skepticism, but it would be good to hear if anything mentioned in this issue strikes at use cases they have.

I would also be happy to participate in a meeting or email discussion on this topic involving more framework representatives.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/747#issuecomment-372906352