-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(kernel): Correct null handling in JSON types #523
Merged
Merged
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
The serialization of structs creates a jackson ObjectNode to pass down to the serialization layer, however those are turned to JSON without processing and are not honoring the inclusion setting to ignore nulls. Added some code in the Java generator to stop adding null values into the ObjectNode.
RomainMuller
changed the title
fix(pacmak/java): Stop serializing
fix(kernel): Correct null handling in JSON types
Jun 7, 2019
null
rix0rrr
approved these changes
Jun 7, 2019
RomainMuller
added a commit
to aws/aws-cdk
that referenced
this pull request
Jun 7, 2019
There are a couple of places where fields accept values that are typed as `Json` per the JSII type specification. This conveys that literal `null` values may be passed and need to be preserved (as far as JSII is concerned - see aws/jsii#523). However in the CloudFormation domain, `null` is semantically equivalent to `undefined`. Now enters Javascript's confusing type system, where `null` is an `object` that cannot be converted to `object` (you read this correctly): ```js typeof null === 'object' // => true Object.entries(null); // => Thrown: // TypeError: Cannot convert undefined or null to object // at Function.entries (<anonymous>) ``` So this changes the `undefined` checks to the `null`-coercing way, so that `null` and `undefined` are handled the same way.
RomainMuller
added a commit
to aws/aws-cdk
that referenced
this pull request
Jun 7, 2019
There are a couple of places where fields accept values that are typed as `Json` per the JSII type specification. This conveys that literal `null` values may be passed and need to be preserved (as far as JSII is concerned - see aws/jsii#523). However in the CloudFormation domain, `null` is semantically equivalent to `undefined`. Now enters Javascript's confusing type system, where `null` is an `object` that cannot be converted to `object` (you read this correctly): ```js typeof null === 'object' // => true Object.entries(null); // => Thrown: // TypeError: Cannot convert undefined or null to object // at Function.entries (<anonymous>) ``` So this changes the `undefined` checks to the `null`-coercing way, so that `null` and `undefined` are handled the same way.
4 tasks
rix0rrr
pushed a commit
to aws/aws-cdk
that referenced
this pull request
Jun 7, 2019
There are a couple of places where fields accept values that are typed as `Json` per the JSII type specification. This conveys that literal `null` values may be passed and need to be preserved (as far as JSII is concerned - see aws/jsii#523). However in the CloudFormation domain, `null` is semantically equivalent to `undefined`. Now enters Javascript's confusing type system, where `null` is an `object` that cannot be converted to `object` (you read this correctly): ```js typeof null === 'object' // => true Object.entries(null); // => Thrown: // TypeError: Cannot convert undefined or null to object // at Function.entries (<canonymous>) ``` So this changes the `undefined` checks to the `null`-coercing way, so that `null` and `undefined` are handled the same way.
This was referenced Aug 22, 2019
This was referenced Dec 12, 2019
This was referenced Dec 13, 2019
This was referenced Jan 20, 2020
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.
The JSON types were serialized "as-is" without touch, meaning if the
value was
null
, it would be forwarded asnull
, instead ofundefined
.This caused some CDK usage patterns to crash at runtime. This changes
the behavior so that top-level
null
s in JSON types turn intoundefined
,while
null
s nested in the JSON value will be preserved (they are validJSON after all!).
Additionally, tuned the Java code generator a little:
The serialization of structs creates a jackson ObjectNode to pass down
to the serialization layer, however those are turned to JSON without
processing and are not honoring the inclusion setting to ignore nulls.
Added some code in the Java generator to stop adding null values into
the ObjectNode.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.