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
Describe the bug
In V4 if you got any exception of ServiceException type, you could clearly identify what's happening from the logs or debug events, because it had a short description of the error (I guess when ToString() was called).
What we have now with V5 is ODataError type which looks like this, when it's raised:
Microsoft.Graph.Models.ODataErrors.ODataError: Exception of type 'Microsoft.Graph.Models.ODataErrors.ODataError' was thrown.
I cannot determine from logs what happened during the call, without creating a handler for this error and find the message through the ODataError.Error.Message object.
I suggest that ODataError should show the basic details of the error when it's thrown, so we can analyse information during debug or reading the application logs. Otherwise we need to wrap every Graph call with a try catch to extract the error message or add a middleware.
The text was updated successfully, but these errors were encountered:
Describe the bug
In V4 if you got any exception of ServiceException type, you could clearly identify what's happening from the logs or debug events, because it had a short description of the error (I guess when ToString() was called).
What we have now with V5 is ODataError type which looks like this, when it's raised:
I cannot determine from logs what happened during the call, without creating a handler for this error and find the message through the ODataError.Error.Message object.
I suggest that ODataError should show the basic details of the error when it's thrown, so we can analyse information during debug or reading the application logs. Otherwise we need to wrap every Graph call with a try catch to extract the error message or add a middleware.
The text was updated successfully, but these errors were encountered: