Bumping back to inbox, since this got tagged for the 1.34 release, which makes it urgent.
I just realized that SpecialReplaceText has a direct reference to old_text. That needs to be fixed as well.
Fri, Sep 20
Thu, Sep 19
This RFC has entered the Last Call period per the TechCom meeting on September 18. The last call will end on October 2nd. If no issues remain unaddressed by that time, this RFC will be approved as proposed.
Moved by to TechCom inbox. I have updated the task description to reflect the current state of the proposal. The draft for the stable interface policy can be found at https://www.mediawiki.org/wiki/Stable_Interface_Policy. If there are no objections, I think the draft can go on Last Call next week. Please put any comments or questions here rather than the talk page on the wiki. I'm more likely to see them here, and they are in context of the prior discussion.
Putting this in the RFC inbox for discussion.
Wed, Sep 18
Proposal needs an update, I plan to do this next week.
Untagging TechCom, since this has been decoupled from the text table and content table.
Tue, Sep 17
The link cache is for the title -> id lookup. Seems to me like you need the opposite here. The batch interface would be Title::newFromIDs (note the plural), but that does no caching.
Mon, Sep 16
T196575: Add block cookie for browser-based API edits (including VisualEditor & MobileFrontend) seems to indicate that we need to be able to manipulate the response (cookies) from the context of block management as well.
Fri, Sep 13
Thu, Sep 12
@osorio-juan-microsoft Thanks, that does sound like it would be difficult to do this in an extension. And if we (WMF) don't enable it, it probably wouldn't need an RFC. But if we are planning to enable it on WMF sites, it will need a closer look.