Summary

Tpt

Would it be possible to define a slot for ProofreadPage, beside the main slot, with format 'json'?— Mpaa (talk) 20:11, 6 February 2019 (UTC) Hi! Sorry for the misunderstanding. Using a slot for the JSON representation is imho a bad idea because it would mean to duplicate the content in the storage system and override a bunch of MediaWiki logic to make sure that the wikitext and JSON representations say in sync. MediaWiki assumes that slots could be edited separately so, e.g. we would have to override the editing API and other parts to make sure to edit the other slot at the same time.
Source: Wikisource

Tpt

Tank you very much! It is a very nice idea. Some points: You can request and save Page: pages content in a JSON format where the header/footer and body are slpit. So you would avoid to have some bad splitter code.
Source: Wikisource

Tpt

If the level change to 3 to 4 the user should change (e.g. the person that set the level to 4 should be different than the one that set it to 3) . The code: https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FProofreadPage.git/ceed34484b48049e2b7d3f9370b05caac486646e/ProofreadPage.body.php#L604 In fact I think that ProofreadPage should do the work of changing the user nameinstead of requesting the API user to do it as it is currently done with the web editing interface.
Source: Wikisource

Get perspective with Kwize: daily news enlightened by great literature