Refactor properties to nullable types for improved flexibility in authentication models

[armando-rodriguez-cko]

This pull request updates several model classes to improve type safety and better represent optional fields in the authentication and response objects. The main changes involve converting many value-type properties to nullable types, updating collections to use more specific types, and aligning enum and custom type usage. These changes help prevent default value confusion and improve serialization/deserialization, especially for optional API fields.

Type safety improvements for model properties:

• Changed various numeric, boolean, and date properties in AccountInfo, MerchantRiskInfo, ThreeDsRequestorAuthenticationInfo, and related classes to nullable types (long?, bool?, DateTime?, etc.), ensuring that optional fields are accurately represented and preventing unintended default values. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]

• Updated collection properties from IList<object> to IList<string> in response classes such as Certificates, GoogleSpa, and Threeds, providing clearer type expectations for serialized data. [1] [2] [3]

Custom type and enum usage improvements:

• Changed string properties representing currency and country codes to use custom types (Currency?, CountryCode?) for better validation and type safety in MerchantRiskInfo and Metadata. Also updated enum usage to nullable where appropriate. [1] [2] [3]

Constructor and default value handling:

• Updated constructors and default value assignments for properties like DaysBetweenPayments and ChannelDataType to use nullable types, ensuring optionality is respected and default values are explicit. [1] [2] [3] [4]

Miscellaneous improvements:

• Added necessary using statements for custom types and JSON serialization attributes to support new property types and serialization requirements. [1] [2] [3] [4]

Response model updates:

• Updated the GetSessionDetailsResponseOk class to use more appropriate types for amount, completion flags, and authentication details, improving accuracy and clarity of session responses. [1] [2] [3] [4] [5] [6]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
28.8% Duplication on New Code

See analysis details on SonarQube Cloud