Last modified: 2014-02-09 04:27:03 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55212, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 53212 - API : add param to filter notifications
API : add param to filter notifications
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Echo (Other open bugs)
unspecified
All All
: Unprioritized enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-08-22 13:07 UTC by Dr Brains
Modified: 2014-02-09 04:27 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Dr Brains 2013-08-22 13:07:35 UTC 
In API module "meta=notifications", 

1) There is not (yet) possibility to check only new notifications that the user have not yet seen.

It would be good to provide a new param ("&notshow=" ?) to do so, with possible values : "all" (default value), "read" and "!read".

2) The provided timestamps ("mw" attribute in timestamp tag and "read" attribute in notification tag) are not in standard mediawiki API timestamp format : "yyyy-mm-ddThh:mm:ssZ" (see for example "list=recentchanges&rcprop=timestamp").

It would be good to fix that too.
Comment 1 Dr Brains 2013-08-22 13:19:23 UTC 
3) It would be good to have time params to filter notifications, based on a timestamp, like in "list=logevents" module :

  lestart             - The timestamp to start enumerating from
  leend               - The timestamp to end enumerating
  ledir               - In which direction to enumerate
                         newer          - List oldest first. 
                         older          - List newest first (default).
Comment 2 Andre Klapper 2013-08-22 14:41:07 UTC 
For future reference, please only file one request per report. Thanks! :)
Comment 3 Dr Brains 2013-08-27 16:40:41 UTC 
@Andre Klapper : 

As the three request are about the same thing (the notifications API module), it seemed good to me to group theses reports and to let the same (group of) developper(s) work on the whole request, as I guess the code modifications to do are in the same area.

But OK, next time I'll do one request per bug.
Comment 4 spage 2013-09-23 20:47:13 UTC 
Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/236
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links