Private account: @LucasWerkmeister.
Currently mainly working Mondays and Tuesdays.
Since I’m running out of other things to do, I’ll take a stab at implementing one suggestion for such an API module.
What’s the problem with including the names in the user language in the API output? That doesn’t feel ugly to me.
I’d prefer if we could make this public, yes. I don’t think there’s any need to keep it private (the public commit makes the issue fairly clear anyways).
That’s the VisualEditor welcome (i18n) – VE probably shouldn’t be running on that page, should it?
From the screenshot it looks like a “welcome to $wiki” banner is blocking the “submit” button:
Does it make sense to treat this like labels and descriptions for items, with the lemmas as label and the gloss as description? Mockup:
Moved to dedicated task T201841: Remove feature to disable RDF export per entity type, closing this one.
I’ve updated the change, and it’s not clear to me what else is required under “more love”, so moving back to review :)
I looked into this a bit, and I think I see two main problems:
Thanks, should I rebase the patch against master and upload it on Gerrit as a regular change? (I assume we don’t need to bother with a pre-release announcement or anything for this extension.)
From 841609dd7263793e3ec4b765aab7468b11b3de5e Mon Sep 17 00:00:00 2001 From: Lucas Werkmeister <email@example.com> Date: Tue, 7 Aug 2018 17:42:25 +0200 Subject: [PATCH] SECURITY: HTML-escape form representations
We can probably completely remove the feature to disable RDF export for some entity types, not just revert the config for lexemes.