Change Details

While porting this to webpack, I couldn't help but notice how redundant this is. It adds indirection to our code and provides additional convenience methods such as inUserBucketA, getGroups and getEditCount We should explore porting those 3 methods to core if they are useful or removing them from our codebase entirely. = Acceptance criteria [] inUserBucketA not used by Minerva or MobileFrontend. Remove it. [] getGroups not used by Minerva or MobileFrontend. Remove it. [] getEditCount should be added to mw.user in core and used in Minerva (skins.minerva.mainMenu/schema.js, skins.minerva.editor/init.js) and MF (mobile.editor.common/EditorOverlayBase.js ). []

While porting this to webpack, I couldn't help but notice how redundant this is. It adds indirection to our code and provides additional convenience methods such as inUserBucketA, getGroups and getEditCount We should explore porting those 3 methods to core if they are useful or removing them from our codebase entirely. = Acceptance criteria [] inUserBucketA not used by Minerva or MobileFrontend. Remove it. [] getGroups not used by Minerva or MobileFrontend. Remove it. [] getEditCount should be added to mw.user in core and used in Minerva (skins.minerva.mainMenu/schema.js, skins.minerva.editor/init.js) and MF (mobile.editor.common/EditorOverlayBase.js ).

While porting this to webpack, I couldn't help but notice how redundant this is. It adds indirection to our code and provides additional convenience methods such as inUserBucketA, getGroups and getEditCount We should explore porting those 3 methods to core if they are useful or removing them from our codebase entirely. = Acceptance criteria [] inUserBucketA not used by Minerva or MobileFrontend. Remove it. [] getGroups not used by Minerva or MobileFrontend. Remove it. [] getEditCount should be added to mw.user in core and used in Minerva (skins.minerva.mainMenu/schema.js, skins.minerva.editor/init.js) and MF (mobile.editor.common/EditorOverlayBase.js ). []