Roan Kattouw bfbfa6be62 Sort wikis by timestamp of most recent notification ... Both in the order of the cross-wiki bundles themselves, and in the message in the notification body. ForeignNotifications tracks timestamps per wiki per section, and exposes these through getWikiTimestamp(). ApiEchoNotifications adds these timestamps to the sources manifest, and also sorts the list of wikis by timestamp (it'd be nicer to do this in ForeignPresentationModel instead, but then we'd have to create a new ForeignNotifications instance which causes a duplicated DB query). NotificationsModel receives the timestamp for its wiki as its fallback timestamp, and makes getTimestamp() return this value during the pre-population phase. This causes its parent to automatically sort it correctly. Because the timestamp of a wiki depends on the section (alerts vs messages), we can't put it in the global sources manifest at the top level of the API response. Instead, get rid of this global sources manifest and put all the sources data in the foreign notifications directly. This allows us to specify different timestamps, and also allows us to get rid of code in EchoApi that was already remapping the API response to this format. Bug: T130298 Change-Id: Ie083fbb1ccaf74fbe804633d87ef03c9e71b120f		2016-03-17 14:21:16 -07:00
..
mw.echo.api.APIHandler.js	Have mw.echo.api.APIHandler.markItemRead actually return a promise	2016-03-14 15:23:08 -07:00
mw.echo.api.EchoApi.js	Sort wikis by timestamp of most recent notification	2016-03-17 14:21:16 -07:00
mw.echo.api.ForeignAPIHandler.js	Echo API layer	2016-03-03 23:40:12 +00:00
mw.echo.api.js	Echo API layer	2016-03-03 23:40:12 +00:00
mw.echo.api.LocalAPIHandler.js	Allow mark-as-unread in notifications	2016-03-11 14:05:10 -08:00
mw.echo.api.NetworkHandler.js	Echo API layer	2016-03-03 23:40:12 +00:00