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
Previously we rejected the idea of using an enum for the ArangoDB error codes, see: #15
However it would still be useful to include an enum in the repository that can be used for doing comparisons, even if the types themselves continue to use int. This could then be used in code such as:
try
{
// do stuff
}
// cast ArangoDbErrorNum to `int` for comparison
catch (ApiErrorException ex) when (ex.ApiError.ErrorNum == (int)ArangoDbErrorNum.DocumentNotFound)
{
// handle not found
}
The text was updated successfully, but these errors were encountered:
Previously we rejected the idea of using an enum for the ArangoDB error codes, see: #15
However it would still be useful to include an enum in the repository that can be used for doing comparisons, even if the types themselves continue to use
int
. This could then be used in code such as:The text was updated successfully, but these errors were encountered: