From 7c860ff967fbae157dd37c9894214e2d732e8f58 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Date: Tue, 22 Nov 2022 17:06:15 +0000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Travis Ralston --- changelogs/client_server/newsfragments/1239.clarification | 2 +- data/api/client-server/event_context.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/changelogs/client_server/newsfragments/1239.clarification b/changelogs/client_server/newsfragments/1239.clarification index ef5500f1..f2c403d1 100644 --- a/changelogs/client_server/newsfragments/1239.clarification +++ b/changelogs/client_server/newsfragments/1239.clarification @@ -1 +1 @@ -Clarified that /context always returns 'event' even if limit is zero. Contributed by @sumnerevans at @beeper. +Clarify that `/context` always returns `event` even if `limit` is zero. Contributed by @sumnerevans at @beeper. diff --git a/data/api/client-server/event_context.yaml b/data/api/client-server/event_context.yaml index 659aea41..4a2541a6 100644 --- a/data/api/client-server/event_context.yaml +++ b/data/api/client-server/event_context.yaml @@ -60,7 +60,7 @@ paths: The maximum number of context events to return. The limit applies to the sum of the `events_before` and `events_after` arrays. The requested event ID is always returned in `event` even if `limit` is - 0. Default: 10. + 0. Defaults to 10. x-example: 3 - in: query name: filter