Closed alsoscotland closed 3 weeks ago
should have a fix out by tomorrow
fixed in https://www.npmjs.com/package/shippo/v/2.3.4
just FYI, this represents a targeted change but we're moving to enums on input, strings on output. most of the enums we have in the spec will actually evolve over time, and since enums are a closed set, if an sdk receives a value it doesn't understand, the call will explode. to sidestep this issue, we're going to drop enums from our output models altogether, so you'll hopefully stop seeing this type of error in the near future.
I am seeing another zod error on the response of a
shipments.create
request. I am passing a previously validated objectId in the addressTo field and receiving the followingHere is the objectId result of the request "object_id": "4eb9cd1bcf9242baa3143bc9f31c394b", "object_created": "2024-06-12T19:31:43.405Z", "object_updated": "2024-06-12T19:31:44.827Z",
and I am sending the object id of a previously validated address which has the following validation results
objectid: 4347bcce24a94f77893ee72ce05ce10b "validation_results": { "is_valid": true, "messages": [ { "source": "addresses_ms", "code": "address_abbreviation_fixed", "text": "The address abbreviation was changed (such as \"Street\" to \"St\")", "type": "address_correction" } ] }