Use a format
for Date
when relevant.
#1531
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Implement a better generation of the OpenAPI date type through the use of
format
for String.It is defined by: https://swagger.io/docs/specification/data-models/data-types/#string
Use
date-time
for iso8601.Use
date-time
for custom RFC3339date-time
.Use
date
for custom RFC3339full-date
.Motivation and Context
There has been issues reported with the date serialization with Kitura (#1529 )
The proper generation should allow for a better mocup generation also, which is always important when making your own server.
How Has This Been Tested?
The tests for Date in OpenAPI have been extended to include:
iso8601
case if the platform supports it.Checklist: