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. [] A getEditBucket method 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). = Developer notes It seems the edit count is most frequently used for bucketed editing counts. A bucketed and standardised edit count in core would be super useful to support existing and future schemas. Instead of upstreaming `getEditCount ` we might instead choose to upstream `getEditBucket` from Popups. We'd need to update MobileWebMainMenuClickTracking to use an edited bucket count.

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. [] Update existing usages of the user module to use mw.user = Developer notes It seems the edit count is most frequently used for bucketed editing counts. A bucketed and standardised edit count in core would be super useful to support existing and future schemas. Instead of upstreaming `getEditCount ` we might instead choose to upstream `getEditBucket` from Popups. We'd need to update MobileWebMainMenuClickTracking to use an edited bucket count. See T210106.

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. [] A getEditBucket method 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).Update existing usages of the user module to use mw.user = Developer notes It seems the edit count is most frequently used for bucketed editing counts. A bucketed and standardised edit count in core would be super useful to support existing and future schemas. Instead of upstreaming `getEditCount ` we might instead choose to upstream `getEditBucket` from Popups. We'd need to update MobileWebMainMenuClickTracking to use an edited bucket count. See T210106.