This shall be a proof of concept implementation of "deep linking" to a particular paragraph (see T400335), needed for using Edit Checks as Edit Suggestions.
The deep link shall contain an article oldId, a paragraph number, and paragraph plaintext to match fuzzily.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Allow triggering checks on a specific ContentBranchNode | mediawiki/extensions/VisualEditor | master | +26 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | ppelberg | T392954 [FY25-26] WE 1.1: Increase constructive edits | |||
| Open | KStoller-WMF | T396162 [EPIC] Revise Tone: Structured Task (WE1.1.2, FY25-26) | |||
| Declined | dchan | T400335 Determine how best to enable deep linking into an Edit Check of a specific range | |||
| Resolved | dchan | T403072 Create proof of concept for launching VisualEditor from a "deep link" |
Change #1190824 had a related patch set uploaded (by Divec; author: Divec):
[mediawiki/extensions/VisualEditor@master] Allow triggering checks on a specific ContentBranchNode
Test wiki created on Patch demo by MGrosse-WMF using patch(es) linked to this task:
https://2f3545fe76.catalyst.wmcloud.org/w/
Test wiki on [[ | Patch demo ]] by MGrosse-WMF using patch(es) linked to this task was deleted:
Test wiki on Patch demo by MGrosse-WMF using patch(es) linked to this task was deleted:
Change #1190824 abandoned by Divec:
[mediawiki/extensions/VisualEditor@master] Allow triggering checks on a specific ContentBranchNode
Reason:
Proof of concept only
Following discussion, we decided the final implementation should use a different technique (subclassing).