Magic Tag Output Filters should support optional Parameters for those functions

[PodsBot]

Magic Tag Output Filters should support optional Parameters for those functions submitted via Slack by jimtrue

[jimtrue]

At present Magic Tag Out Filters (functions ran against the magic tag contents) don't support anything but the function name, ie {@field_name, output_function}

Proposing adding the ability to pass parameters in that format:
{@field_name, output_function, parameters (multiple, comma separated)}

And it would pass along to the calling function as:
output_function($field_name, $parameters...);

[m9n]

This was my fault :)

I was specifically thinking of allowing PHP date formatting on date/time fields.

I could argue that this is just as important when building templates with date/time fields as multiple image sizes are for image fields.

But if Jim's suggestion meets this use case and others as well, that would be cool :)

[tomas-eklund]

Even though I can absolutely see the benefit of being able to pass parameters to filter functions (my current use case also being able to format dates differently in various situations), I would like to propose a different syntax than what is being suggested above.

The reason being that I would find it even more useful being able to chain different filter functions like you can do in Twig:

{@field_name, filter_function, format_function, escape_function}

Also, my OCD does not like the position-based format suggested, where the first position is reserved for the field name and the second a filter function while the third, fourth and following positions are used for parameters.

I would much prefer using a syntax that can allow for parameters as well as chaining. Something like this:

{@field_name, filter_function(parameter_1; parameter_2), escape_function}