In T204366#9740463, @RheingoldRiver wrote:

I've also used a setup that I call Module:ForwardArgs to accomplish something like this. I think the most minimal example would look like:

function p.main(frame)
  return frame:expandTemplate{ title = frame.args.template, frame:getParent().args }
end

And it gets used in the code of Template:MyTemplate like:

{{#invoke:forwardArgs|main|template=mySubtemplate}}

A slightly more robust implementation can be found here; someone wanted the "prefix" functionality that Extension:Loops provides in its forargs parser function so I added support for that too.

In T297671#12295757, @Izno wrote:

In T297671#12295719, @ExE-Boss wrote:

In T297671#8373080, @Izno wrote:

You should ideally be authoring with TemplateStyles these days, which will better guarantee your order.

Unfortunately, not all wikis have that installed (pre‑1.44) or enabled (1.44 or later).

TemplateStyles has been available since 1.30 which was released in 2017, nearly a decade ago. Every supported version of MediaWiki can run TemplateStyles. The set of hosts documented at mwwiki:Extension:TemplateStyles is most of the large ones. So I'm not sure what this comment is actually about.

A better option would be to add a function to check whether the expensive function count can be incremented up to n times, something like:

lua
--- @param amount? number
--- @return number
function mw.canCallExpensiveFunctions(amount)
	libraryUtil.checkType("mw.canCallExpensiveFunctions", 1, amount, "number", true);
	amount = amount or 1;

In T78465#9731598, @Tacsipacsi wrote:

File description pages can exist without a file existing (manually created pages in the File namespace) and files can exist without description pages existing (Commons files without local description pages), so title.exists and title.file.exists are independent. I propose declining this task.

In T297671#8373080, @Izno wrote:

You should ideally be authoring with TemplateStyles these days, which will better guarantee your order.

In T361934#12103106, @FeRDNYC wrote:

There are some real concerns regarding composition, I'm not trying to deny that. For instance, this:

:root {
  --var1: 'pr0n.gif';
  --var2: url(var(--var1));
}
#el {
  background: var(--var2);
}

...is a valid rule for setting the element's background-image-source to url('pr0n.gif'), but it's not particularly hard to detect that when parsing the custom properties themselves, since we never want to allow any url() values at all. Custom properties do not really make it any easier to hide those invalid values, since the substitution results are never fed back into the CSS parser.

Note that the MediaWiki Download ships with CodeEditor, but not CodeMirror, so that needs to be rectified for MediaWiki 1.46.

In T364685#11465285, @Mr._Starfleet_Command wrote:

Is this token-merging indeed possible?

In T384685#11676043, @Escargot_rouge wrote:

There isn't any templatedata for Template:Template link general, so there is nohing to expect to be loaded from templatedata for the redirect either.

In T418268#11647068, @cscott wrote:

I'm curious why they didn't just use the HTML entity expansion in the template definition.

That’s because the new stylesheet is not yet deployed on Wikipedia.

This directly conflicts with: T285463: FuzzyBot should automatically create wanted categories that are marked for translation