Open nakamorichi opened 5 years ago
@darrelmiller Can you point this issue to respective endpoint team ?
@NakulSabharwal any update on this? This is generating redundant error handling logic to get the error based on string search of the exception message.
Thank you for reporting this issue. This appears to be an issue or limitation with the service APIs. Unfortunately, as the Microsoft Graph SDK team, we do not have ownership of the APIs that are causing you issues. We invite you to create a question about the service API to Microsoft Q&A and tagged with one of the [microsoft-graph-*] tags, that way it will get routed to the appropriate team for them to triage:
https://aka.ms/msgraphsupport or directly https://aka.ms/askgraph
For now, we will close the issue on our side but feel free to open it in the relevant repository if you think the issue is specific to SDK. Please let us know if this helps!
Note: We will close this repository on April 19, 2024.
Expected behavior
GraphError::isError
should match error codes defined inenum GraphErrorCodes
with the codes returned by the API.Reference: https://docs.microsoft.com/en-us/graph/errors#code-property
Actual behavior
The method fails to match the error codes. For example, following request:
The above request tries to fetch a non-existent event from an existing calendar. The error code does not match with the code defined in the API reference (correct one would be
itemNotFound
) nor does it match with the one defined in the enum,ITEM_NOT_FOUND
.