issue#144 throwing proper error message for badge assertion in issuer api

[pradeepmurugesan]

No description provided.

[travisbot]

This pull request passes (merged 4237178 into e1998fd).

[stenington]

I'm a little nervous to rely solely on the error message here, unless we're certain that all error responses have sensible messages. I'd either like to beef up the testing around that, or add some sort of "We've encountered the following problem:" text to preface error.message. At least that way if it's blank or undecipherable, it's not just totally empty.

[stenington]

Hey @pradeepmurugesan, this looks pretty good. There are two little fixes I'd think would be good to add before merging, but I think I can leave the request open and you can add a commit to it.

[travisbot]

This pull request passes (merged 46cf0e6 into e1998fd).

[pradeepmurugesan]

@stenington : Fixed as per the comments
@brianloveswords : we already discussed about adding the error message as the reason, but I feel this is more convincing like adding the reason as INACCESSIBLE and the exception message as a new component "message".

[stenington]

Thanks!