Open wujekbogdan opened 8 years ago
It should be fairly easy to include the raw response as part of the exception, but the point of exceptions in cases like this is to abstract away the underlying specificity and instead include your own messages/codes.
When the exception is thrown by the
message->invoke()
method then I'm unable to get the error code. The only thing I can get is$e->getMessage()
that returns just an error message string.It would be good if there was a method that returns the native Nexmo response
Correct me if I'm wrong.
// Edit:
This is how i solved the problem, but this is not an elegant solution at all.