JADE will need to support the basic antivandalism extensions before we can deploy.
Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Tests to demonstrate SpamBlacklist integration | mediawiki/extensions/JADE | master | +118 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | awight | T206255 SpamBlacklist integration for JADE | |||
| Resolved | awight | T206346 Support wikitext in judgment notes and endorsement comment fields |
Event Timeline
As long as JADE is registering external links with ParserOutput in the standard way, there should be no extra changes needed for SpamBlacklist integration.
Thanks for these breadcrumbs, I'll write a test to see whether it works out of the box.
Change 464727 had a related patch set uploaded (by Awight; owner: Awight):
[mediawiki/extensions/JADE@master] [WIP] Tests for SpamBlacklist integration
So far, it's looking like we'll need to mess with ParserOutput hooks. I don't understand what's involved yet, only that we're in an awkward position with snippets of wikitext inside JSON fields. Maybe we can parse each snippet, extract the links and external links, then add to a top-level ParserOutput object?
Normally this is done in Content::fillParserOutput(), which manipulates a ParserOutput object. I would assume that JADE is going to override that function whenever it implements a proper UI instead of relying on the JSON table output.
Thanks, it's helpful to have this confirmation! Let me invite you to the WIP patch where I'm trying to do this :-D
https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/JADE/+/464737/
btw, someone recently pleaded with me to stop using Mustache, but I wasn't able to follow up to learn more. Maybe you can comment in code review if there's something better I should know about? This doesn't seem like a good use for OOUI, if that's the only alternative…
Change 464727 merged by jenkins-bot:
[mediawiki/extensions/JADE@master] Tests to demonstrate SpamBlacklist integration