- From: Pascal Vos <notifications@github.com>
- Date: Mon, 31 Mar 2025 07:07:04 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 31 March 2025 14:07:08 UTC
vospascal left a comment (WICG/webcomponents#1069) > [@vospascal](https://github.com/vospascal) I definitely would not propose changing template literals at this point. This would be purely a DOM API, and not require any changes to JS. > > But what could `$expressionFunction{expression}` do that `${expressionFunction(expression)}` can't? well i `${expressionFunction(expression)}` is more inside the expression side of things and i feel is always evaluates/computes. if you would do `$expressionFunction{expression}` you might be able to do some pre evaluation/computation things like potentialy life cycles or something i dont think that would make sense if you put it `expressionFunction` inside the `{}` also the template tag suggestion of having a binding syntax like `{{}}` in my opinion would be nice if it would match the template literal expression syntax so `${}`. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/1069#issuecomment-2766355738 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/1069/2766355738@github.com>
Received on Monday, 31 March 2025 14:07:08 UTC