Change Details

Currently, WebRequest::getLimitOffset accepts an optional default limit, and an optional option name, as parameters. There should be a user parameter accepted, and eventually, required. To clarify that the function gets the limit and offset //for a specific user//, I suggest: * Create WebRequest::getLimitOffsetForUser ** Which requires a user to be passed, and continues to accept the limit and option name * Convert WebRequest::getLimitOffset to a wrapper that simple uses `$wgUser` * Replace uses of ::getLimitOffset with ::getLimitOffsetForUser * Remove ::getLimitOffset

Currently, WebRequest::getLimitOffset accepts an optional default limit, and an optional option name, as parameters. There should be a user parameter accepted, and eventually, required, when accessing user preferences. To clarify that the function gets the limit and offset //for a specific user//, I suggest: * Create WebRequest::getLimitOffsetForUser ** Which requires a user to be passed to get the user preference for an option * Convert WebRequest::getLimitOffset to a wrapper that simple uses `$wgUser` * Replace uses of ::getLimitOffset with ::getLimitOffsetForUser, supplying a user when needed * Remove ::getLimitOffset

Currently, WebRequest::getLimitOffset accepts an optional default limit, and an optional option name, as parameters. There should be a user parameter accepted, and eventually, required, when accessing user preferences. To clarify that the function gets the limit and offset //for a specific user//, I suggest: * Create WebRequest::getLimitOffsetForUser ** Which requires a user to be passed, and continues to accept the limit and to get the user preference for an option namen * Convert WebRequest::getLimitOffset to a wrapper that simple uses `$wgUser` * Replace uses of ::getLimitOffset with ::getLimitOffsetForUser, supplying a user when needed * Remove ::getLimitOffset