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
{{ message }}
This repository has been archived by the owner on Nov 26, 2017. It is now read-only.
Would it be appropriate to all a logger to Github, or add a callable to log debugging information for an exception. The callable could be set in the Github options so that we don't have to couple it to LoggerAwareInterface, but I'm also ok with that coupling. In the case above, we could dump the response object to the logger and try and decipher what went wrong.
The text was updated successfully, but these errors were encountered:
Sometimes there isn't enough information about why a request fails.
https://github.com/joomla/joomla-framework/blob/staging/src/Joomla/Github/AbstractGithubObject.php#L127
Would it be appropriate to all a logger to Github, or add a callable to log debugging information for an exception. The callable could be set in the Github options so that we don't have to couple it to
LoggerAwareInterface
, but I'm also ok with that coupling. In the case above, we could dump the response object to the logger and try and decipher what went wrong.The text was updated successfully, but these errors were encountered: