Describe the bug
When using vs2022 and connected service for the checkoutservice v71 openapi spec NSwag generator doesn't work correctly with nullability if not 'nullable: true' is present on the property.
I have had to manually change properties after my requirements to handle this. For instance in the /sessions endpoint (CreateCheckoutSessionRequest) I had to add 'nullable: true' to storePaymentMethod, enableRecurring, enableOneClick, expiresAt to be able to use the client without having a session causing error with payment.
To Reproduce
Steps to reproduce the behavior:
Download checkoutservice v71 yaml add add to folder in assembly
Add connectedservice using the yaml (with option GenerateNullableReferenceTypes:true present)
The generated client have bool instead of bool? for instance
Expected behavior
Expecting nullable properties to be reflected correctly in the generated client
Screenshots
Need to add this to all properties if possible
Describe the bug When using vs2022 and connected service for the checkoutservice v71 openapi spec NSwag generator doesn't work correctly with nullability if not 'nullable: true' is present on the property. I have had to manually change properties after my requirements to handle this. For instance in the /sessions endpoint (CreateCheckoutSessionRequest) I had to add 'nullable: true' to storePaymentMethod, enableRecurring, enableOneClick, expiresAt to be able to use the client without having a session causing error with payment.
To Reproduce Steps to reproduce the behavior:
Expected behavior Expecting nullable properties to be reflected correctly in the generated client
Screenshots Need to add this to all properties if possible![image](https://github.com/Adyen/adyen-openapi/assets/25958942/91329e92-c28c-4fa2-9c1d-2dd61194e52a)