Front-end standards group/2018-02-28

From MediaWiki.org
Jump to navigation Jump to search

Attending: Volker E., Andrew R.-G., Joaquin O.-H., Jan Dr.

Action & Code[edit]

New quests[edit]

T138401: Replace jsduck with JSDoc3 across all Wikimedia code bases This is now already in place in Parsoid and close to production in OOjs/OOUI. Improving and unify theme is one of the blockers right now.

https://phabricator.wikimedia.org/T187672 Create a “Wikimedia” theme for JSDoc3

T107561: MediaWiki support for Composer equivalent for JavaScript packages. Continued inputs

T185295 Enforce 80-100 characters line length with eslint in eslint-wikimedia-config Waiting for group consensus: 80 seems more useful to terminal users and is the rule for a few other big companies out there, 100 is enforced by phpcs and devs would have to switch conventions when going between projects. (I'd lean therefore to 100, even when I'd like to see 80 enforced everywhere)

A Phabricator poll would be a way too, I don't have access to make one.

https://phabricator.wikimedia.org/T187672

Successes[edit]

Social[edit]

FYI[edit]

Reading Web might be interested in TemplateStyles for fixing mobile page issues phab: https://phabricator.wikimedia.org/T159262 some bg research/notes: https://www.mediawiki.org/wiki/Reading/Web/Mobile_page_issues https://www.mediawiki.org/wiki/User:JDrewniak_(WMF)/notes/Improving_Mobile_page_issues Also looking at options like adding RDFa data to templates for easier parsing