JanZerebecki added a comment.
I know I'm repeating myself, but for some this is probably not a repeat: This is reimplementing part of what Mediawiki provides, but at the same time is not further along nor provides any advantage over what Mediawiki provides. Mediawiki its JS module loader correctly implements more than what this task is about. The code needed to display the WDQS GUI on a special page would be small. One thing isn't solved for Mediawiki: A step that runs npm to pull in JS components. I started https://phabricator.wikimedia.org/T133388 (an RFC) for that. But the WDQS GUI repo doesn't implement that either. I'd suggest moving the WDQS GUI to a Mediawiki extension, as that is required for some things we want to do in the future anyway. @Jonas do you want to go that route? --- Yes, as pointed out, deploying WDQS requires more manual steps since the gui repo was created. I would have liked for it to get more automated instead. Please remember that this is a production service, other people need to be able to contribute and need to deploy security fixes. For my taste that would require being capable of continuous deployment. TASK DETAIL https://phabricator.wikimedia.org/T133026 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Smalyshev, JanZerebecki Cc: gerritbot, daniel, TerraCodes, Gehel, Lydia_Pintscher, JanZerebecki, Jonas, Aklapper, Avner, Lewizho99, Maathavan, debt, D3r1ck01, FloNight, Izno, jkroll, Smalyshev, Wikidata-bugs, Jdouglas, aude, Deskana, Manybubbles, Mbch331 _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
