Making this blocked by T75863 for now, but potentially instead we could have a hacky second parameter to wfLoadExtension instead.

Also related to this ticket then I guess is T88258.
I'm not sure if either one of these tickets however is the right thing to do here to help solve this ticket.

Note that we have another global functions to load several extensions from an array. So instead of:

foreach ($extensionsToLoad as $index => $extension) {
	wfLoadExtension( $extension );
}

One can use the plural variant of that function:

wfLoadExtensions( $extensionsToLoad );

MediaWiki installer via maintenance/install.php --with-extensions does inject wfLoadExtension() calls, I think in a sorted by name order. We caught several load ordering issues a while back, but most should have been caught by now.

I wonder if some concept of "subextensions" would be worth adding the extension registration.
I would see this working for wikibase as extension.json in the root of the repo then points to 2 more extension.json files in sub directories.
Not sure if there are any other use cases for this though?

In T239137#5692560, @Addshore wrote:

I wonder if some concept of "subextensions" would be worth adding the extension registration.
I would see this working for wikibase as extension.json in the root of the repo then points to 2 more extension.json files in sub directories.
Not sure if there are any other use cases for this though?

It's a massive anti-pattern, so I seriously hope there aren't many use cases. ;-) ConfirmEdit has this – we have:

	wfLoadExtension( 'ConfirmEdit' );
	wfLoadExtension( 'ConfirmEdit/FancyCaptcha' );

… but I think that's incompatible with the directory structure you've picked for Wikibase (and won't work on Windows machines, oh well, how sad).

Not sure why that would be incompatible with the wikibase directory structure?
It sound like something like this could work.

	wfLoadExtension( 'Wikibase/repo' );
	wfLoadExtension( 'Wikibase/client' );

Also, not sure why this wouldn't work on windows?

I'm also not saying we don't necessarily want to do T75863, however, I don't think that really blocks this ticket.
However is wfLoadExtension is wanted, then T88258 definity blocks this ticket.

In T239137#5696351, @Addshore wrote:

Not sure why that would be incompatible with the wikibase directory structure?

Maybe it would?

It sound like something like this could work.

	wfLoadExtension( 'Wikibase/repo' );
	wfLoadExtension( 'Wikibase/client' );

Also, not sure why this wouldn't work on windows?

The / would need to magically turn into a \, which they won't.

I'm also not saying we don't necessarily want to do T75863, however, I don't think that really blocks this ticket.
However i[f] wfLoadExtension is wanted, then T88258 definity blocks this ticket.

True; I'll add T88258 and not remove T75863 for now, until we get further towards resolution.

I don't think there's much benefit to actually doing this, I guess you save 100 function calls. But extension registry already does this internally, wfLoadExtension queues everything up into one array and then loads it later on.