each* string functions about sprig HOT 5 OPEN

I think this could be useful, especially with multi-arg support. Would you see a version of this wherein the templates the user could simply do each "trim" <args> (trim just being an example, replace with whatever function) in addition to the each* you are suggesting

from sprig.

I believe that would either require reflection or a big switch which would in turn call the actual function. It could work, but in my experience explicit function calls work better in this case. Since there is a pattern, it's really easy to guess the behavior.

But yeah, that could work.

from sprig.

@sagikazarmark What would the template functions be, what would they work on, and why those things?

I'm trying to understand the end user need and what would be solved.

The technique looks interesting and I could see uses. Just trying to understand why and how to bake it in here. The why and what it solves is important.

from sprig.

I came looking for something like this. Actually I wanted to runprintf over elements of a list. I've ended up having to implement my own mapPrintF function but it would have been much more convenient to have just been able to write e.g. {{ map "printf" "values-%s.yaml" .myList }} to return a list where each element has been modified by the printf function. In fact, functional constructs in general (map, reduce, filter, etc.) would be super handy...

from sprig.

@mattfarina sorry, but I don't remember what the use case was.

I guess the idea is that you can output a list of strings, but apply some filters to it first? Unfortunately I rarely use templates these days. :\

from sprig.