To be clear appropriate usagesinclude:
- $wmgUseRelatedArticles is valid as there is no global $wgUseRelatedArticles.
- $wmgUseRelatedArticles and $wmgRelatedArticlesShowInSidebar;are valid as their values change depend on $wmgUseRelatedArticles
Anything that doesn't depend on the value of something else can be shifted to drop the m
It's highly possible in doing this task we discover all use cases are valid.
Current usages that I see:
Assuming that appropriate usage is only for things that are not actually config variables (unless noted otherwise) this narrows the audit considerably.
'wmgPopupsBetaFeature' - Looking at that list PopupsBetaFeature depends on the value of UseBetaFeatures so is appropriately used.
wmgExtractsRemoveClasses - looks like this can be removed as dates back to TextExtracts pre-extension loading
wmgExtractsExtendOpenSearchXml - simple boolean. No reason to use wmg
wmgMFEditorOptions - redunant this is true by default
'wmgRelatedArticlesShowInSidebar and wmgRelatedArticlesShowInFooter depend on each other so this makes sense
wmgRelatedArticlesFooterWhitelistedSkins - exists due to T142663
What do you think @Dereckson ?