Last modified: 2014-04-19 05:15:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T57752, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55752 - Migrate MediaWiki core jsduck settings to work with JSDuck 5
Migrate MediaWiki core jsduck settings to work with JSDuck 5
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Documentation (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: 1.23.0 release
Assigned To: Krinkle
:
Depends on:
Blocks: 55753
  Show dependency treegraph
 
Reported: 2013-10-15 20:11 UTC by Krinkle
Modified: 2014-04-19 05:15 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2013-10-15 20:11:51 UTC
JSDuck has introduced various new annotations (such as @fires to complement @event which we're already using). However 4.x and 5.x is a pretty significant upgrade so we should make sure we're compatible and there are no regressions before we upgrade.
Comment 1 Krinkle 2014-04-19 05:10:45 UTC
Related changes:

- Support JSDuck v5.x
  Change-Id: Ie6649a3e39457bde7a0d8bd00da8ea53e76e3085
Comment 2 Krinkle 2014-04-19 05:12:22 UTC
Related changes:

- mediawiki.Title: Correct documentation structure for Title.exist
  Change-Id: If0c66e6e8a904769ee857c1ee94377dc13000d41
Comment 3 Krinkle 2014-04-19 05:15:38 UTC
Related changes:

- mediawiki-core-jsduck: Switch over to using the refreshed script
  Depends on Ie6649a3e39457bde7 in mediawiki-core.
  Change-Id: I39785a2ba80b4230170c1794b1fc354ca0efd7dd

This was the last required change. Though the previous two changes in mediawiki-core did enough to make it jsduck v5 compatible, the jenkins job was still using the jsduck/config.json file directly instead of the maintenance script (which has where jsduck v4/v5 compat switch is).

We're now safe to upgrade.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links