Add support for LocalTime and OffsetTime #234
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #233
Add support for
LocalTimeandOffsetTimeinTypeUtil. This includes a simpleexampleas well asexternalDocsfor each (see the test JSON for the result).LocalTimeuses format"local-time", whereasOffsetTimeuses"time", which seemed in alignment with the OAS 3 spec section on data types. Each use a description and link forexternalDocsthat matches that ofdateanddate-timein the spec as well.This also switches
TypeWithFormatto a builder pattern to allow extension of default schema attributes without additional constructor permutations.