BP-603: Use custom nswag templates to fix dateonly parsing and formatting in generated API. #1
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
msljivic
changed the title
msljivic
changed the title
avanwaas
approved these changes
Dec 6, 2023
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.
Use custom nswag templates to fix dateonly parsing and formatting in generated api.
DateOnly parameter in URL/querystring is serialized with time.
NSwag/issues/3958
Template: Client.RequestUrl.liquid
Date only format is interpreted as UTC when passed to the Date constructor
NJsonSchema/issues/1480
Template: ConvertToClass.liquid