Originally discussed in this futures entry, Mechanic's action definition model has been expanded to a new
"meta"
package of information. Using this, developers may annotate actions with context for later debugging, or with decision-making information to be used during followup mechanic/actions/perform events.An action's meta information is defined as a peer to its type and options, being given at the same top level of the action object JSON. To facilitate this, the Liquid action tag has a new, zero-argument block syntax, whose body is used as the body of the action object itself.
This feature was requested by the community, and defined in collaboration; its arrival enables task flows that are more expressively nuanced, while using less code overall.
Read more