Some comments updated + more tests

[david-ruiz-cko]

This pull request standardizes the documentation for property constraints across multiple entity classes by replacing inconsistent constraint descriptions (like <= 256 characters or >= 0) with a uniform format (max 256 characters, min 0, etc.). Additionally, it introduces new unit tests to ensure correct serialization of ACH instrument details and issuing dispute requests.

Key changes include:

Documentation consistency improvements:

• Updated property constraint comments throughout entity classes to use a consistent format, such as max N characters, min N, and max N, instead of mixed inequality symbols. This affects fields for string length, numeric ranges, and other constraints in classes like DelegatedPaymentBillingAddress, CardholderRequest, Order, AmountAllocationCommission, PaymentSetupBillingDescriptor, PaymentSetupRequest, and various dispute and card request classes. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]

Testing improvements:

• Added InstrumentDetailsAchSerializationTest.php to verify round-trip serialization and correct Swagger value output for ACH instrument account types.
• Added DisputeRequestsSerializationTest.php to test serialization of dispute request objects, including fraud details and evidence, and to ensure fraud type values map exactly to Swagger definitions.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud