Re: [w3c/webcomponents] [templates] Template proposal essentials (shave the mustache) (#739)

What example? I don't see any example which doesn't involve scripts here. See https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Declarative-Custom-Elements-Strawman.md for how the current proposal does this.

What you're proposing would require ordering of properties to substitute $$ or whatever delimiter is, and doesn't allow name-based referencing. This alone is a show stopper in declarative custom elements since you'd have to remember which argument corresponds to which part based on ordering. In the world where a template is defined away from where it's used having to remember what n-th argument means in the template poses a serious if not fatal developer ergonomics issue.

-- 
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/739#issuecomment-368213182