Random thought: providing contextual params in action.

[bennadel]

Just thinking out loud here. Right now, from what I understand, *-param attributes are static. Would there be any value in allowing them to reference a controller-scoped value? I'm thinking specifically here in terms of cross-controller communication. Perhaps we could use the # to denote a controller-scoped value, much like we do with the data-action syntax. Maybe something like:

data-foo-id-param="bar#id" -> Passes bar.id into foo method (in event.params).

data-foo-bar-param="bar#" -> Passes bar into foo method (in event.params).

If I can argue against myself for a moment, this is a terrible idea because it seeks to make the Controller instance the source of truth for a value when the DOM should be the source of truth for a value (if I understand the Hotwire mentality correctly).

Also, at least in this case, the value of .id could presumably be made available via server-side rendering of the template:

data-foo-id-param="{{ id }}"

... so, it shouldn't need to use the controller reference.

Anyway, just thinking out loud, and trying to evolve my Angular brain into a Hotwire brain (slowly).