The editing interface for collaborationhubs does not check for or handle edit conflicts, because it can't unless this is all reimplemented from scratch.
Very basic functionality (check and warn if anything is found, even if all it is is a newer edit) should be sufficient for general use cases until something is more properly abstracted upstream.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Isarra | T116831 Women in Red workflow automation / optimization (tracking) | |||
| Declined | None | T106828 Make it easier for WikiProjects to shove long, narrow lists into columns | |||
| Declined | None | T106823 Discourage wikiprojects from shoving extra stuff into their headers | |||
| Resolved | Isarra | T97210 MediaWiki extension for WikiProjects / on-wiki working groups | |||
| Invalid | None | T137916 Detect CollaborationListContent pages and format output for those pages | |||
| Declined | None | T155680 Deploy CollaborationKit to all Wikipedias | |||
| Declined | None | T123028 Deploy CollaborationKit on English Wikipedia | |||
| Resolved | Reedy | T138326 Deploy CollaborationKit on Test Wikipedia | |||
| Resolved | None | T138325 Deploy CollaborationKit on Beta Wikipedia | |||
| Resolved | Reedy | T138324 Security review for CollaborationKit | |||
| Resolved | Harej | T123977 [Basic Functionality] Create editing interface for CollaborationHubContent content model | |||
| Duplicate | None | T131474 Editing conflict handling in Special:EditCollaborationHub |
Of course I'm getting a little ahead of myself in that the editing interface doesn't actually exist yet, but by the the time that happens I'll forget this was even something we would want, let alone that it's not there.
Reasonable request, considering you *can* edit CollaborationHubContent pages, albeit by editing raw JSON. So edit conflict checking is an issue.
Discussed with @daniel. Because of how EditPage is set up, edit conflict check and edit conflict resolution are not abstracted from the wikitext editing interface. Meaning we would have to implement our own. There may be other things where this is the case as well. I recommend for now that we implement the most basic edit conflict check and that's it.
The long term solution may be T120414.
Just check and warn. Should be more than sufficient for how often edit conflicts are likely to happen... in the, er, currently intended use cases, but of course some crazy morons may start using it as a forum or something...