You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Properties that should be nullable are not listed as nullable if they are reference types.
For example, in a session s, s.AmountTotal is correctly Nullable<int64>, but s.ClientReferenceId is a string when it should be a string?.
Discrepancy between:
Presumably this library was never updated to support nullable reference types.
I would estimate it would take 2x longer to write dotnet code without nullable reference types, since for every use of a property you would need to refer to the online documentation to see if it is nullable or not and add manual casts to nullable before proceeding.
To Reproduce
Get a Session s
Type s.ClientReferenceId
The result is a string
Expected behavior
The result should be a string?.
Code snippets
No response
OS
Windows
.NET version
dotnet9
Library version
current
API version
current
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Properties that should be nullable are not listed as nullable if they are reference types.
For example, in a session
s
,s.AmountTotal
is correctlyNullable<int64>
, buts.ClientReferenceId
is astring
when it should be astring?
.Discrepancy between:
stripe-dotnet/src/Stripe.net/Entities/Checkout/Sessions/Session.cs
Line 95 in a18e87f
Presumably this library was never updated to support nullable reference types.
I would estimate it would take 2x longer to write dotnet code without nullable reference types, since for every use of a property you would need to refer to the online documentation to see if it is nullable or not and add manual casts to nullable before proceeding.
To Reproduce
Session s
s.ClientReferenceId
string
Expected behavior
The result should be a
string?
.Code snippets
No response
OS
Windows
.NET version
dotnet9
Library version
current
API version
current
Additional context
No response
The text was updated successfully, but these errors were encountered: