This repository was archived by the owner on Jun 13, 2018. It is now read-only.
Save description for UPS shipment event in message #359
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About
For the other carrier adapters, we always save something for the
messageof aShipmentEvent-EventinmessageEventDescriptionevent-descriptioninmessageUPS doesn't do anything, and just gives it a
nilvalue. Rather thannilthe 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 inmessagefor eachShipmentEvent.Testing
Added another unit test in
test/unit/ups_test.rbto verify the existence ofmessagefor each shipment event in a response.@kmcphillips @mdking @RichardBlair @MalazAlamir