Bug 17620 - Fix format of date/data-times in Swagger definition
Summary: Fix format of date/data-times in Swagger definition
Status: RESOLVED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Web services (show other bugs)
Version: master
Hardware: All All
: P5 - low normal (vote)
Assignee: Tomás Cohen Arazi
QA Contact: Testopia
URL:
Keywords:
Depends on: 17621 17607
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-14 06:19 UTC by Martin Renvoize
Modified: 2023-07-04 14:52 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Bug 17620: Patron - Add date format definitions (2.03 KB, patch)
2016-11-14 06:58 UTC, Martin Renvoize
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize 2016-11-14 06:19:46 UTC
Bug #17607 highlighted the lack of a defined format for date and date-time fields in our api responses.  We should settle on a response form and validate it to ensure it's consistently given across the codebase.
Comment 1 Martin Renvoize 2016-11-14 06:58:45 UTC
Created attachment 57468 [details] [review]
Bug 17620: Patron - Add date format definitions

This patch adds 'format' fields to date type fields in the Patron
definition.
Comment 2 Martin Renvoize 2016-11-14 06:59:20 UTC
I'll be going through each existing api route and attaching a patch per route as required.
Comment 3 Katrin Fischer 2020-01-11 16:09:37 UTC
Still valid?
Comment 4 Tomás Cohen Arazi 2020-01-11 17:59:19 UTC
I think I fixed then all in several reviews. Specially when we introduced the RFC process for all endpoints, existing and new. But let me re-check.
Comment 5 Katrin Fischer 2023-06-25 14:54:19 UTC
(In reply to Tomás Cohen Arazi from comment #4)
> I think I fixed then all in several reviews. Specially when we introduced
> the RFC process for all endpoints, existing and new. But let me re-check.

2.5 years... can we assume FIXED? :)
Comment 6 Jonathan Druart 2023-07-04 14:52:54 UTC
Yes, this is fixed now.