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

>From the Angular end: This approach is definitely in the right direction for us - while we're not interested in using the proposed high-level syntax (it's simply too different / doesn't cover the breadth of our API), the `const { content, parts } = someTemplate.cloneWithParts()` is an API I can reasonably see us building on top of. 

I'd echo @JanMiksovsky's question as well - it would seem to me that `AttributePart` is a bit of a special case - unless you're going to provide `PropertyPart` and `EventListenerPart`(probably not!), everything could be implemented on top of `NodeTemplatePart`.

The exception to this is `InnerTemplatePart` - again, it feels a bit opinionated (instead of say, `HoleInTheTemplatePart` or something) - Angular inserts a comment node to fulfill this case today.

I recognize that the `AttributePart` is likely necessary for the high level declarative API in the original proposal, so I don't see it as a blocker or anything - in general, the layering proposal is pretty exciting!


-- 
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-375096080