-
Notifications
You must be signed in to change notification settings - Fork 862
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
IVS mutator type does not match backing field type #3487
Comments
This behavior is expected in the current version of the .NET SDK (i.e. 3.7.x), but we fixed this in the next major version (V4) which is currently in preview and can be tracked in #3362; Here's the relevant section of the announcement blog post:
For example, here's how the
|
Comments on closed issues are hard for our team to see. |
@dscpinheiro Thanks for the response. |
Describe the bug
Example:
As the mutator is non-nullable i am not able to assign
null
to_endTime
and thus not able to mock the different possible responses from the API.This seems to be a general issue, stemming from how the code is being auto generated.
Or maybe value types are always marked as nullable? In that case i would expect to be able to define the property as nullable in
generator/ServiceModels/ivs/ivs-2020-07-14.normal.json
I wanted to look at a fix myself but its not quite clear where/how the autogeneration happens.
Expected Behavior
I would expect the mutator type to match the backing field type to be able to simulate diffrent possible responses from the IVS API.
AWS .NET SDK and/or Package version used
AWSSDK.IVS 3.7.400.23
Targeted .NET Platform
.net 8
Operating System and version
MacOS Sononoma 14.0
The text was updated successfully, but these errors were encountered: