You’re not alone in wanting it! There’s an (in-progress) RFC aiming for “splarguments”. Two notes:
-
In the future, with a template “strict mode” (see the WIP RFC here), dynamic invocation will be a bit different: it will not be string-based, but will require you to actually pass a reference to a specific component. There will be a good design to support this, though: template imports at a minimum will be helpful for enabling it.
-
Given (1), I think you’ll just be able to use ABC to pass components around; if and insofar as we still have something like
{{component}}
I think the need for it would be limited to doing partial-application-of-arguments (the way{{fn}}
does for functions).
I’d like to see “splarguments” land, as I think they make a lot of “decorator”-style component patterns dramatically nicer, and as such they’ll be a substantial quality-of-life improvement. Definitely still some serious design work to be done there, though.
In the meantime, one could definitely write an addon which supplies an AST transform that makes ...@args
work. Doing so might in fact be really helpful input for the design of that RFC! What works? What doesn’t? What are the weird edge cases? etc.