Exception Handling Issue during International Address Verification

[mrnevisane]

Exception Handling Issue during International Address Verification

[alies-dev]

I can confirm: I have similar issues:

Invalid value 'Housenumber/Building' for 'coverage', must be one of 'SUBBUILDING', 'HOUSENUMBER/BUILDING', 'STREET', 'LOCALITY', 'SPARSE'

and

Invalid value 'Subbuilding' for 'coverage', must be one of 'SUBBUILDING', 'HOUSENUMBER/BUILDING', 'STREET', 'LOCALITY', 'SPARSE'

Exception message is confusing

Example of API response:

{
    "id": "intl_ver_bf83dde51d4d738acd4a",
    "recipient": "John Zorn",
    "primary_line": "THE UNIVERSITY OF MELBOURNE, THOMAS CHERRY BUILDING, LEVEL 1",
    "secondary_line": "",
    "last_line": "MELBOURNE VIC 3010",
    "country": "AU",
    "coverage": "Subbuilding",
    "deliverability": "deliverable_missing_info",
    "status": "2",
    "components": {
        "primary_number": "",
        "building": "",
        "street_name": "THE UNIVERSITY OF MELBOURNE, THOMAS CHERRY BUILDING, LEVEL 1",
        "locality": "",
        "city": "MELBOURNE",
        "state": "VIC",
        "postal_code": "3010"
    },
    "object": "intl_verification"
}

Please note to the "coverage": "Subbuilding" part - it has a wrong case (should be SUBBUILDING)

But \OpenAPI\Client\Model\IntlVerification::getCoverageAllowableValues returns uppercase options only:

And similar issue with \OpenAPI\Client\Model\IntlVerification::setStatus method: API uses numeric values (1, 2, 3, 4), but this method accepts only string values prefixed by LV:

I'll create a PR to solve both issues

UPD: Sorry, it's not possible to fix \OpenAPI\Client\Model\IntlVerification::setStatus on this library level: when this method accept a numeric string (e.g. 1), we don't how to properly prefix the string because there are few possible prefixes (LV, LF, LM, LU. see the screenshot above). So, the only solution is to fix server response or lose IntlVerification validation in setCoverage and setStatus methods

version: v4.2.3 (latest)