Use @warning instead of WARNING: for better markup

WARNING:

Right, I was wondering the same. We could just implement the getters so that they call these things directly.

But then I'm also wondering what's the purpose of KCModuleInfo at all and whether we could just use KPluginInfo directly instead -- but that's a KF6 consideration, since it's part of the API for KCMultiDialog and others.

Well, we could add a addModule(KPluginInfo) overload if that's the direction we're going for; I just don't have full overview on the KCM stuff.

It's complicated.

1. If you use the QString constructor, you know service() is usable. That's the case for all users of KCModuleInfo except KCModuleLoader. [Not that there are many]

2. Even KCModuleLoader calls service(), to test for noDisplay().

The whole concept of NoDisplay only makes sense for desktop files, unless we want to have that in JSON metadata as well. I suppose we do, but this currently seems to be completely missing (e.g. from KPluginMetaData, if we want this in all plugins, not just KCMs). We'd have to duplicate the logic currently in KService::noDisplay().

Any volunteers to look into this? :-)

As I just ran into this code, a short reminder: it would be a regression not to have a noDisplay check in the case of pure JSON metadata, as the current code of KService::;noDisplay() also asks KAuth whether the page should be shown (KAuthorized::authorizeControlModule(storageId())), which some KIOSK systems or admins might rely on, but also showInCurrentDesktop() & showOnCurrentPlatform(), which also still make sense, for what I can tell.