Make Option
non-required & add required
attr
#530
Merged
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.
Make
Option
fields non-required by default. This is the way it used to be originally but was changed due hopes for better client code generation. However since it caused issues with client side generation the behaviour is now changed back on this commit.The nullability behaviour will still stay to same, so
Option
will still be considered nullable. These rules are explained in the docs for greater detail.This commit also adds
required
attribute that can be used to declare a field ofToSchema
andIntoParams
as required in order to change the default required status of a field / parameter.Since
Option
is by default non-required, this would enforce thename
parameter to be required.Fixes #529