Adds configuration settings to influence required annotation#1563
Open
tsinghammer wants to merge 1 commit intoRicoSuter:masterfrom
Open
Adds configuration settings to influence required annotation#1563tsinghammer wants to merge 1 commit intoRicoSuter:masterfrom
tsinghammer wants to merge 1 commit intoRicoSuter:masterfrom
Conversation
|
is this available for merge @RicoSuter ? this seettings seems useful instead of having to register a custom serializer to allow nullable properties (openapi schemas can often be unprecise in the real world) |
|
Hitting RicoSuter/NSwag#3851 issue.. can anyone help with ETA for fix?? |
This file contains hidden or 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
5 participants
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.
Sometimes it would be useful, also with an OpenApi3 schema to generate non-required fields as Required.Default.
Do you think it makes sense to follow such a toggle and elaborate it more?