Change Details

To quote https://www.mediawiki.org/wiki/Manual:Parser_functions#Named_parameters : > Parser functions do not support named parameters the way templates and tag extensions do, but it is occasionally useful to fake it. For uniformity of template syntax parsing, and to prevent continued slightly-incompatible wheel reinvention, we should fix this. When a parser function is registered with `SFH_NAMED_ARGS` as a flag to [`Parser::setFunctionHook`](https://www.mediawiki.org/wiki/Manual:Parser_functions#The_setFunctionHook_hook) standardized parsing of named arguments should be done by core. Users should be encouraged to migrate to this. We should think carefully through the desired behavior for whitespace-stripping of argument values, and ensure it makes sense with {T114432}.

To quote https://www.mediawiki.org/wiki/Manual:Parser_functions#Named_parameters : > Parser functions do not support named parameters the way templates and tag extensions do, but it is occasionally useful to fake it. For uniformity of template syntax parsing, and to prevent continued slightly-incompatible wheel reinvention, we should fix this. When a parser function is registered with `SFH_NAMED_ARGS` as a flag to [`Parser::setFunctionHook`](https://www.mediawiki.org/wiki/Manual:Parser_functions#The_setFunctionHook_hook) standardized parsing of named arguments should be done by core. Users should be encouraged to migrate to this. We should think carefully through the desired behavior for whitespace-stripping of argument values, and ensure it makes sense with {T114432}. (Note that argument values for extension tags is whitespace-stripped in core, which is arguably a misfeature: T267974#6625861 )

To quote https://www.mediawiki.org/wiki/Manual:Parser_functions#Named_parameters : > Parser functions do not support named parameters the way templates and tag extensions do, but it is occasionally useful to fake it. For uniformity of template syntax parsing, and to prevent continued slightly-incompatible wheel reinvention, we should fix this. When a parser function is registered with `SFH_NAMED_ARGS` as a flag to [`Parser::setFunctionHook`](https://www.mediawiki.org/wiki/Manual:Parser_functions#The_setFunctionHook_hook) standardized parsing of named arguments should be done by core. Users should be encouraged to migrate to this. We should think carefully through the desired behavior for whitespace-stripping of argument values, and ensure it makes sense with {T114432}. (Note that argument values for extension tags is whitespace-stripped in core, which is arguably a misfeature: T267974#6625861 )