-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Java (jsii): passing "null" behaves differently than no argument #157
Labels
language/java
Related to Java bindings
Comments
eladb
referenced
this issue
Jun 21, 2018
I guess the issue stems from the fact that the Java runtime passes |
Is this still an issue? |
I think it is |
eladb
pushed a commit
to aws/jsii
that referenced
this issue
Nov 7, 2018
Since most languages do not have a distinction between "null" and "undefined", jsii will effectively convert any "null" value passed into an argument, a property or inside an object to "undefined". Adds a compliance test to Java and .NET called "NullShouldBeTreatedAsUndefined". Fixes aws/aws-cdk#157 Fixes #282
eladb
pushed a commit
to aws/jsii
that referenced
this issue
Nov 7, 2018
Since most languages do not have a distinction between "null" and "undefined", jsii will effectively convert any "null" value passed into an argument, a property or inside an object to "undefined". Adds a compliance test to Java and .NET called "NullShouldBeTreatedAsUndefined". Fixes aws/aws-cdk#157 Fixes #282
eladb
pushed a commit
to aws/jsii
that referenced
this issue
Nov 7, 2018
Since most languages do not have a distinction between "null" and "undefined", jsii will effectively convert any "null" value passed into an argument, a property or inside an object to "undefined". Adds a compliance test to Java and .NET called "NullShouldBeTreatedAsUndefined". Fixes aws/aws-cdk#157 Fixes #282
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example:
The text was updated successfully, but these errors were encountered: