-
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
.NET: null property object support #282
Labels
language/dotnet
Related to .NET bindings (C#, F#, ...)
Comments
IIRC this was a bug in the underlying library TypeScript source for some constructors. Check whether this is the case before trying to fix this at the generator level. |
eladb
pushed a commit
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
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
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
From @costleya – Requiring code to pass around empty StackProps() param is confusing. This is a bug in the .NET binding generation code.
The text was updated successfully, but these errors were encountered: