Skip to content
This repository was archived by the owner on Jun 13, 2018. It is now read-only.

Conversation

@jonathankwok
Copy link
Contributor

About

For the other carrier adapters, we always save something for the message of a ShipmentEvent -

UPS doesn't do anything, and just gives it a nil value. Rather than nil the value, we can do what USPS and FedEx do and pass in the event description.

This change will keep the carriers consistent with each other.

Changes

Simply store the text in the 'Status/StatusType/Description') node in message for each ShipmentEvent.

Testing

Added another unit test in test/unit/ups_test.rb to verify the existence of message for each shipment event in a response.

@kmcphillips @mdking @RichardBlair @MalazAlamir

@RichardBlair
Copy link
Contributor

:shipit: on 💚

@mdking
Copy link
Contributor

mdking commented Apr 26, 2016

👍

@kmcphillips
Copy link
Contributor

Change looks good! Let's get the build fixed out of band first though.

@jonathankwok jonathankwok force-pushed the non-nil-ups-event-messages branch from a3fbdc9 to ef4d734 Compare April 27, 2016 15:59
@jonathankwok jonathankwok merged commit 85ae7b5 into master Apr 27, 2016
@jonathankwok jonathankwok deleted the non-nil-ups-event-messages branch April 27, 2016 16:50
maartenvg pushed a commit that referenced this pull request Nov 9, 2017
Save description for UPS shipment event in message
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants