We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CoreHttpProvider.processResponse catches GraphServiceExceptions and writes the exception explicitly with logger.error.
This is not needed because the exception is also thrown afterwards (and can be handled individually by the caller).
The explicit logging should be removed so that the GraphServiceException is no longer written to log in each case.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. Would you be willing to submit a pull request to address this?
Sorry, something went wrong.
Explicit log to error removed (as described in microsoftgraph#885)
453fa4f
Thanks for the quick response. I submitted pull request #898
Merge pull request #898 from MaHa6543/dev
145f064
Explicit log to error removed (described in issue #885)
Successfully merging a pull request may close this issue.
CoreHttpProvider.processResponse catches GraphServiceExceptions and writes the exception explicitly with logger.error.
This is not needed because the exception is also thrown afterwards (and can be handled individually by the caller).
The explicit logging should be removed so that the GraphServiceException is no longer written to log in each case.
The text was updated successfully, but these errors were encountered: