CU 2.0: Namespace Service Name
Closed, ResolvedPublic
Actions

Description

To avoid name conflicts, the service name should be prefixed with the extension's name.

Related Gerrit Patches:

mediawiki/extensions/CheckUser : master

Status	Assigned	Task
Open	None	T139810 RFC: Overhaul the CheckUser extension
Open	Niharika	T236225 [Epic] CheckUser 2.0 Improvements
Open	Niharika	T237039 [Epic] CheckUser 2.0: Preliminary check
Open	Prtksxna	T237299 CU 2.0: Sticky highlighting in Preliminary check and Compare tabs
Open	Niharika	T237593 [Epic] CheckUser 2.0: Compare
Open	None	T175587 Add a user-agent parser to CheckUser
Resolved	Reedy	T239259 Security Review for whichbrowser/parser
Open	None	T174553 Create a mechanism that allows fetching geolocation and subnet data for IP addresses
Open	None	T36438 Reverse DNS lookup
Open	None	T234980 Implement an option to highlight non-standard user-agent strings in CheckUser
Open	dmaza	T238714 CU 2.0: Fetch information to be displayed in Compare tab
Open	Prtksxna	T238782 CU 2.0: Display data in the Compare tab
Open	None	T237300 CU 2.0: Sorting in the Compare tab
Open	None	T237298 CheckUser 2.0: Display the data fetched on special page (preliminary check)
Open	dmaza	T237296 CheckUser 2.0: Create service and methods for new CU extension
Resolved	dbarratt	T239682 CU 2.0: Namespace Service Name
Open	None	T238808 CU 2.0: Pagination in the compare tab
Open	None	T238809 CU 2.0: Filters in the Compare tab

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptTue, Dec 3, 4:16 AM

Change 554230 had a related patch set uploaded (by Dbarratt; owner: Dbarratt):
[mediawiki/extensions/CheckUser@master] Namespace Services

Change 554230 merged by jenkins-bot:
[mediawiki/extensions/CheckUser@master] Namespace Services

I guess this is fine. I don't really know...

In T239682#5709079, @dom_walden wrote:

I guess this is fine. I don't really know...

The service isn't being used yet, so there isn't even a regression to test. :)