It would be nice if we could avoid a page reload in patrolling workflows. Can we do an AJAX style request to jadeproposeorendorse?
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Implemented asynchronous Jade updates on secondary integrations | mediawiki/extensions/Jade | master | +75 -7 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T212435 Review real-world query plans and performance for Jade | |||
| Declined | None | T238877 Write Huggle labels to Jade | |||
| Declined | calbon | T183381 Deploy pilot of Jade to a small set of wikis. | |||
| Resolved | • ACraze | T229974 Implement secondary Jade Integrations | |||
| Resolved | kevinbazira | T212387 Implement Special:Diff integration for Jade | |||
| Resolved | kevinbazira | T253752 [Spike] Explore use of AJAX pattern for secondary Jade integrations |
Event Timeline
Comment Actions
The initial goal was to use AJAX ( either MediaWiki's or jQuery's ) but turns out the Jade API client was able to asynchronously return updated Jade entity data after every Jade action. So we leveraged this to update Jade elements asynchronously and stopped Jade page reloads on secondary integration pages which results into better UX for patrollers.
Comment Actions
Change 599717 had a related patch set uploaded (by Kevin Bazira; owner: Kevin Bazira):
[mediawiki/extensions/Jade@master] Implemented asynchronous Jade updates on secondary integrations
Comment Actions
Change 599717 merged by jenkins-bot:
[mediawiki/extensions/Jade@master] Implemented asynchronous Jade updates on secondary integrations