Am 05.04.20 um 23:18 schrieb Petr Bena:
> But still, I am curious what is the recommended approach for someone
> who wants to develop their application "properly" in a way that it's
> backward compatible? First query the MediaWiki version via API, and
> based on that decide how to call APIs? I can'
Aha thanks for the update. To give you some context, I would like to
fix https://phabricator.wikimedia.org/T249460 the main problem as I
see now, is that this looks like a seriously breaking change to me
(but maybe I am overlooking something). If I change the API call to
work with rvslots, I doubt
Thanks for bringing this up.
I have made some updates to the documentation in mediawiki.org to make clear
that MCR is not work in progress. While support is not complete in all parts of
MediaWiki, the storage layer has been implemented and the database has been
migrated to the new system.
Am 05.0
It is where a page can have multiple content handlers associated with it.
The most common example is commons file pages. They have normal wikitext
page, but they also have a slot containing wikidata-style data structured
data.
Whether or not you have to worry about this depends on what you're doi
Hello,
https://www.mediawiki.org/wiki/API:Revisions mentions "revision slots"
multiple times, but fails to explain what it is?
I noticed that some queries that were running fine in the past now
have warning: "Because "rvslots" was not specified, a legacy format
has been used for the output. This
Hey Szabó,
Thanks for the pointers - much appreciated.
My impression is that the approach you are talking about is great for
creating a high level of integration with Visual Editor. I've looked at
Kartographer which is doing something similar. However at this point I just
want the map JS to be ex
Hi Jeroen,
I think you need to register a custom DM (DataModel)[1] and CE
(ContentEditable)[2] node implementation for this extension tag inside
VisualEditor to control their rendering and how the user can interact with
them. Unfortunately, I am not sure if there is documentation (apart from th