This repository was archived by the owner on Nov 27, 2023. It is now read-only.
"UTF-*" misspelling and new response attribute from Mandrill#14
Merged
cribbstechnologies merged 4 commits intoMay 24, 2013
Merged
Conversation
cribbstechnologies
added a commit
that referenced
this pull request
May 24, 2013
"UTF-*" misspelling and new response attribute from Mandrill
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
I started getting exceptions inside my app because Mandrill had added a new attribute to their responses, "reject_reason". So this pull request has a fix for that.
When I pulled and got the latest changes though, I found that I was getting another crash, and it turns out that "UTF-8" was spelt "UFT-8", leading to IOExceptions being thrown. So I fixed that up in this pull request too :-)
Cheers,
Martin