Make code generation respectful to null values #1210
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.
#1197 fix
Currently if value is
null
orundefined
(checked asvalue ? doSomething(value) : <any>undefined
), it will setundefined
to object if value is null, that's incorrect. If we pass null as value, it should still be null value. That's two different values, including API: for example, ASP.NET core will produce 415 error if you will send empty body (undefined
) instead ofnull
value.The easiest way to fix it without making multiple checks for null and undefined is to just pass data value back if it's
null
orundefined
:value ? doSomething(value) : value