feat: infer_null_optionality
config option
#15
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 📖
Add support for generating TypeScript interfaces with
null
types for optional attributes.Background 📜
null
types are generally more common for APIs because JSON does not serializeundefined
.The Fix 🔨
Added support to specify optionality as one of
true
,:null
, or:undefined_or_null
for more flexibility. Also included ainfer_null_optionality
configuration option (disabled by default for backward compatibility) which will allow the library to determine:null
or:undefined_or_null
where appropriate based on the SQL schema and the use of conditional attributes.Screenshots 📷