aboutsummaryrefslogtreecommitdiff
path: root/releasenotes/notes/api-order-events-by-date-7484164761c5231b.yaml
diff options
context:
space:
mode:
authorJeremy Cline <jcline@redhat.com>2019-10-15 17:30:11 -0400
committerStephen Finucane <stephen@that.guru>2019-11-30 17:00:39 +0000
commite0f3220b3698fa3f9383b8c536a01f57cad8df15 (patch)
tree8e3d3c17047254213851d02801ebe2f59e91cccf /releasenotes/notes/api-order-events-by-date-7484164761c5231b.yaml
parente53d7985a15a90617d653645d1bb0c2693b73ff6 (diff)
downloadpatchwork-e0f3220b3698fa3f9383b8c536a01f57cad8df15.tar
patchwork-e0f3220b3698fa3f9383b8c536a01f57cad8df15.tar.gz
Allow ordering events by date
By default, the events API orders events by date in descending order (newest first). However, it's useful to be able to order the events by oldest events first. For example, when a client is polling the events API for new events since a given date and wishes to process them in chronological order. Signed-off-by: Jeremy Cline <jcline@redhat.com> Reviewed-by: Stephen Finucane <stephen@that.guru>
Diffstat (limited to 'releasenotes/notes/api-order-events-by-date-7484164761c5231b.yaml')
-rw-r--r--releasenotes/notes/api-order-events-by-date-7484164761c5231b.yaml5
1 files changed, 5 insertions, 0 deletions
diff --git a/releasenotes/notes/api-order-events-by-date-7484164761c5231b.yaml b/releasenotes/notes/api-order-events-by-date-7484164761c5231b.yaml
new file mode 100644
index 0000000..5d5328d
--- /dev/null
+++ b/releasenotes/notes/api-order-events-by-date-7484164761c5231b.yaml
@@ -0,0 +1,5 @@
+---
+features:
+ - |
+ Allow ordering events from the events API by date. This can be done by
+ adding ``order=date`` or ``order=-date`` (the default) parameters.