Closed Solanya closed 1 year ago
Only issue I can think of is how likely would it be that someone wants to actually supply a string with a comma as an argument, such as:
{link*onClick(param1=I really, really love bananas!, param2=:fatcat:)*Click for Cookies!}
Might need to require quotes around the value or escaping commas - which leads to possible nightmare cases like this that needs a lot of care to parse:
{link*onClick(param1="I am a "happy" person today... (really!)", param2=":fatcat:")*Click for More Cookies!}
One solution that - given my zero knowledge of Extended might not even be possible - would be that if instead of passing the value as a literal string to the target workflow, the link instead pass the value assigned to a variable of the same name from whatever object hosted the link to begin with; for example given:
{link*onClick(param1=var1, param2=var2)*Click for no cookies.}
Would it be at all possible for the hypothetical onClick
workflow to be executed with param1
set to the contents of a variable named var1
that belongs to the object or document that the link was clicked from in any way?
No, because we wouldn't need to set a value in a variable in such a case. I don't particularly mind the edge case, as there is still the current method of making multiple workflows to handle it, and it seems much more unlikely than just having numbers/IDs provided.
Seleves on Discord:
Would rather have a syntax like
onClick(abc, def)
oronClick(param1=abc, param2=def)
for better readability, so need to adjust patterns for this.