Split from T138401: Replace jsduck with JSDoc3 across all Wikimedia code bases.
This is currently blocking us from using es6 features like const in the parts of the code that are covered by jsduck.
We should also use this moment to reconsider whether we actually get use out of that documentation. Neither WikibaseLexeme not EntitySchema has generated JavaScript documentation.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T263914 Offer TypeScript declaration files for the MediaWiki Javascript API (MediaWiki API typings) | ||
| Resolved | hashar | T213282 JSDuck at doc.wikimedia.org loads fonts from google | |||
| Open | None | T334853 Clean up JS code now that we can use ES6 rather than ES5 across all Wikimedia deployed codebases | |||
| Open | KBach | T138401 Replace jsduck with JSDoc3 across all Wikimedia code bases | |||
| Open | None | T342905 Replace jsduck with JSDoc3 in Wikibase |
We should also use this moment to reconsider whether we actually get use out of that documentation.
Apparently it was a fourth birthday present by Jonas and Amir: T133028: [Story] autogenerated Wikibase documentation (and integration/config changes). That said, the link search results all seem to be related to that birthday announcement – I’m not seeing any pages that look like they link to the JS documentation independently for its usefulness.
(The REST API docs under js/rest-api/ are built separately, and I think we could still continue to build those if we stop building the rest of the JS documentation.)