Spread JS event map

[iamajoe]

Sorry in advance in case I have missed an issue related to this.

There are cases where a map[string]templ.ComponentScript might make sense but spreading or iterating is not possible on the attributes side. Tried to do a spread with templ.Attributes but those are not templ scripts so it makes sense that they do not work.

jsMap := map[string]templ.ComponentScript{
  "onclick": alert(),
}

Example A (spread):

<button { jsMap... }>Foo</button>

Example B (for):

<button
for evt, fn := range jsMap {
  {evt}={fn}
}
>Foo</button>

Personally I think it would be better to support a for under attributes. Also, a for even for templ.Attributes would be interesting.

[alehechka]

I have a PR open that adds support for ComponentScripts within the templ.Attributes. There hasn't been much action for review, but with more interest in the feature maybe it can move over the line.

#595

[iamajoe]

Nice. I would say it is still not the best interface since my go to would be to use go syntax but a solution at least and also the "basis" since attributes is like the barebones option.

[joerdav]

I'm going to close this issue for now as script templates are deprecated, we are looking into creating examples of better ways to interact with js in templ, which will hopefully make your use cases easier to implement.

[iamajoe]

I'm going to close this issue for now as script templates are deprecated, we are looking into creating examples of better ways to interact with js in templ, which will hopefully make your use cases easier to implement.

Why is it deprecated? I am actually using it quite a lot. The idea now is to substitute by the script tags, sure works about the same but think about a button onclick for example, it is easier to set through a ComponentScript. Do you have an issue related to this deprecation I could read?

[joerdav]

@iamajoe not yet. Currently there is one for css components, the reasoning is very similar. #740

[joerdav]

The deprecation itself happened under #739