{{ message }}
Repository navigation
Transform Section #8771
Description
Suggestion
Similar to filter sections, but for transforming a list.
transform {_list::*}:
input * 2
abs(input)
Why?
Even though this is achievable by stacking these transformations together in a regular transform effect ({_list::*} transformed using (abs(input * 2))), it provides more options for less standard syntax that doesn't have as easy-to-use expressions.
Other
No response
Agreement
- I have read the guidelines above and affirm I am following them with this suggestion.
Activity
sovdeeth commentedon Jul 13, 2026
I think I would rather avoid just raw expressions hanging out on a line by themselves.
Perhaps a better solution would be to make it a returnable section so it can execute as normal and the returned value is the mapped value.
miberss commentedon Aug 14, 2026
Conditions basically are 2 raw expressions and there was no problem with putting them in the filter or if a(ny|ll).
Would a returnable section be something like this?:
transform {_list::*}: set {_x} to input * 2 return abs({_x})There isn't really any good name you could give to the {_x} variable
Possibly able to mutate input?, for it to look like this
transform {_list::*}: multiply input by 2 return abs(input)novystar commentedon Aug 14, 2026
if input can be changed then return probably isn't necessary
bluelhf commentedon Aug 14, 2026
Big fan of making input support changers, it requires some extra work though
sovdeeth commentedon Aug 14, 2026
Conditions have verbs in them though, so they're valid statements on their own. Expressions do not.
I like the changeable input idea.