WikidataClient needs a UserMergeAccountFields subscriber to support UserMerge.
Version: unspecified
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz67781
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Jdforrester-WMF | T69758 Identify extensions that need updates to work with user merging | ||
| Declined | None | T69781 Add UserMerge support to WikibaseClient | ||
| · · · |
Event Timeline
Comment Actions
Only place we store user data in client are external recent changes... and it's not practicable nor worth it to change those if someone on repo (Wikidata) gets renamed.
Comment Actions
(In reply to Marius Hoch from comment #1)
Only place we store user data in client are external recent changes... and
it's not practicable nor worth it to change those if someone on repo
(Wikidata) gets renamed.
It's not a rename :P
Comment Actions
So, looking at an example inserted row, rc_user is set to 0, and rc_user_text is the user's name at the time of their edit.
The user's id on Wikidata is serialized into the rc_params field. Will anything read from that and try to look up user info for that user? If not, we should be good.
Comment Actions
(In reply to Kunal Mehta (Legoktm) from comment #3)
The user's id on Wikidata is serialized into the rc_params field. Will
anything read from that and try to look up user info for that user? If not,
we should be good.
The user id in there is unused, as it's not needed for formatting.