Page MenuHomePhabricator

Use core edit notices API instead of the VisualEditor API in the iOS app
Open, LowPublic


In task T201596, the edit notices were added to the iOS app by using the internal API of VisualEditor:

We'd like to be able to make breaking changes to that API without consulting anyone. Also, the API output includes a lot of things that are probably irrelevant for the app, and are generated and downloaded unnecessarily. Please change it to use the core API prop=info&inprop=editintro, which I am introducing in T45683.

The new API provides the response in mostly the same format, only slight changes should be needed to call the API with different parameters and read the response from different properties. (But if you're already using the prop=info or prop=revisions API somewhere, you could optimize their use by combining the requests.)