You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we rely on Exceptions being thrown when operations are unsuccessful. This makes using this gem a bit dirty.
An implementation right now would need to rescue specific Exceptions to handle the flow and/or re-raise the Exception.
Opening this issue to come up with a better solution for this, wrapping responses in a Response object that implements success? and encapsulates data returned.
Right now we rely on Exceptions being thrown when operations are unsuccessful. This makes using this gem a bit dirty.
An implementation right now would need to rescue specific Exceptions to handle the flow and/or re-raise the Exception.
Opening this issue to come up with a better solution for this, wrapping responses in a
Response
object that implementssuccess?
and encapsulates data returned.also did a quick poll on twitter
The text was updated successfully, but these errors were encountered: