Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)

@NullVoxPopuli 
> there is no need to know about any footguns, because there would be none (unless someone points out something to me haha).

Do I have this right? Since what you propose would rely on the proposed [JS content tag](https://wycats.github.io/polaris-sketchwork/content-tag.html), it would necessarily involve a compiler and that compiler would be responsible for doing something like wrapping all the signal access in functions, or whatever is needed to ensure the update can be fine-grained.

If so, would you agree the downsides are something like: (1) requires a build step, (2) depends on a robust potentially complex build compiler?

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

Message ID: <WICG/webcomponents/issues/1069/2302236668@github.com>