From 89eeb6fecbfeff5413be17e63936c26e8f8926f1 Mon Sep 17 00:00:00 2001 From: Eric Hoekstra Date: Fri, 21 Jun 2024 11:21:47 +0200 Subject: [PATCH] Date processing specified, processing of periodStart and -End enhanced. --- paths/customer_careprogram.yaml | 5 +++-- schemas/date.yaml | 2 +- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/paths/customer_careprogram.yaml b/paths/customer_careprogram.yaml index 9162125..49053c2 100644 --- a/paths/customer_careprogram.yaml +++ b/paths/customer_careprogram.yaml @@ -48,7 +48,7 @@ post: The care group must be allowed to take responsibility for the practices it holds. If not, the request is ignored and an empty Json-object is send back to the caller. Indicating that processing was not successful. The practice must be one of the care group practices. If not, the request is ignored and an empty Json-object is send back to the caller. In all other cases a Json-object containing the same data as in the request with a timestamp added is send back in the response. - The operation is idem potent for the combination of: `careprogram`, `agb`, `periodStart` and `periodEnd`. If these are the same in any subsequent call the request is processes as being fully accepted, showing the request data in the response, but the `employee` and `timestamp` aren't updated in the database. The timestamp of the original request is added to the response. + The operation is idempotent for the combination of: `careprogram`, `agb`, `periodStart` and `periodEnd`. If these are the same in any _subsequent call_ the request is processes as being fully accepted, showing the request data in the response, but the `employee` and `timestamp` aren't updated in the database. The timestamp of the original submit to this API is added to the response. requestBody: content: 'application/x-www-form-urlencoded': @@ -63,9 +63,10 @@ post: $ref: '../schemas/agb.yaml' periodStart: description: |- - For the API the period start and end are just properties. Only the constraint that periodStart < periodEnd is enforced. + If `periodEnd` is supplied, then the `periodStart` must meet the condition that `periodStart` < `periodEnd`. The period starts on `periodStart` and ends on the day before `periodEnd`, so the start date is inclusive and end date exclusive. $ref: ../schemas/date.yaml periodEnd: + description: See `periodStart`. $ref: ../schemas/date.yaml employee: type: string diff --git a/schemas/date.yaml b/schemas/date.yaml index 7ebc4ab..3368204 100644 --- a/schemas/date.yaml +++ b/schemas/date.yaml @@ -1,4 +1,4 @@ -description: Date without time part in ISO-8601 format. +description: Date without time part in ISO-8601 format. Dates are processed using Java's java.util.GregorianCalender in non-lenient mode. That for example means that 2023-02-29, which was not in a leap year, is intepreted as 2023-03-01. type: string format: date example: "1970-01-13"