Create API to expose editnotices
Closed, ResolvedPublicFeature
Actions

Assigned To

Authored By

	duplicatebug
	Jan 6 2013, 5:21 PM

Description

Editnotices for pages are not currently exposed in the API, but are expected to be used by any interface of a Wikipedia editor. This implies that the information should be easily retrievable.

It should be noted that the VisualEditor api has it's own private implementation of listing all edit notices that should be presented to users: https://en.wikipedia.org/w/api.php?action=visualeditor&format=json&paction=metadata&page=List_of_emoticons&uselang=en&oldid=846338965

This should probably be moved to core as well as be exposed via restbase or something similar.

Version: 1.21.x
Severity: enhancement

Details

Reference: bz43683

	Subject	Repo	Branch	Lines +/-
	Add 'preloadcontent' and 'editintro' in API prop=info	mediawiki/core	master	+167 -3

Customize query in gerrit

Related Objects
Search...

Status	Subtype	Assigned	Task
Resolved		JTannerWMF	T319347 iOS edit notices and errors
Open		None	T278838 Mobile user communication issues ([[Wikipedia:Mobile communication bugs]])
Open		None	T201595 Mobile frontend web does not present edit notices
Resolved	BUG REPORT	JTannerWMF	T201596 iOS app does not present edit notices
Resolved		Dbrant	T201597 Android app does not present edit notices
Open		None	T337100 Use core edit notices API instead of the VisualEditor API in the iOS app
Resolved		Dbrant	T337101 Use core edit notices API instead of the VisualEditor API in the Android app
Resolved	Feature	• matmarex	T45683 Create API to expose editnotices
Resolved		• matmarex	T201613 Unify 'edit notices' technology stack

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:24 AM

• bzimport added a project: MediaWiki-Action-API.

• bzimport set Reference to bz43683.

• bzimport added a subscriber: Unknown Object (MLST).

duplicatebug created this task.Jan 6 2013, 5:21 PM

I wonder whether it would be better for prop=info to return the names of the messages containing the notice instead of parsing them itself. The client could parse these using action=parse if it wants HTML.

The main drawback to parsing them in prop=info is that parsing is expensive; prop=revisions, for example, will error out if asked to parse more than one revision, and if we'd add editnotices with parsed output to prop=info we'd have to do something similar there.

On a side note, I still don't understand what happened with r48276. Per-page edit noticed were half removed, but the removal wasn't finished even after this was pointed out, and then they were added back 2.5 years later.

Change 74963 had a related patch set uploaded by Umherirrender:
Api: Add editnotices to prop=info

https://gerrit.wikimedia.org/r/74963

Change 74963 abandoned by Umherirrender:
Api: Add editnotices to prop=info

https://gerrit.wikimedia.org/r/74963

duplicatebug unsubscribed.Dec 13 2014, 11:50 AM

Anomie moved this task from Unsorted to Needs details or plan on the MediaWiki-Action-API board.Feb 19 2015, 7:15 PM

Anomie moved this task from Needs details or plan to Needs Code on the MediaWiki-Action-API board.

TheDJ renamed this task from Add editnotices to prop=info to Create API to expose editnotices.Aug 9 2018, 9:17 AM

TheDJ updated the task description. (Show Details)

TheDJ removed a subscriber: • wikibugs-l-list.

TheDJ added a parent task: T201595: Mobile frontend web does not present edit notices.Aug 9 2018, 9:22 AM

TheDJ added a parent task: T201596: iOS app does not present edit notices.Aug 9 2018, 9:24 AM