These modules are subclasses of ApiQueryBase and apparently for these you are required to override the constructor in order to set the modify (but there is nothing that enforces anyone to do so etc..

@Anomie Did I conclude that correctly ? Is there something we can do to make this less of a pitfall ?

In T70648#3280468, @TheDJ wrote:

@Anomie Did I conclude that correctly ?

Yes, it seems so.

Is there something we can do to make this less of a pitfall ?

I suppose we could have ApiQueryBase::__construct() throw if the prefix is '', but that wouldn't stop two different extensions' modules from choosing the same prefix and only discovering that in a situation like this.

Or we could drop the prefix uniqueness test in favor of a test that ApiQueryBase modules all have distinct parameter names. Collisions there would be less likely (different prefixes mostly take care of it), but it would still be possible.

We can probably change ApiTranscodeStatus to have a prefix... or kill it entirely in favor of videoinfo/imageinfo. It doesn't appear to actually be used within TMH, and it's not a great interface if anybody's using it.

yeah we used it in the transcode table before. At the moment we seem to just look in the database using queries to achieve the same. Kinda strange :)