-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
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
Documentation: Add exception handling document #1603
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please follow the required format: "[Internal] Category: (Add|Fix|Refactor) Description"
Examples:
Diagnostics: Add GetElapsedClientLatency to CosmosDiagnostics
PartitionKey: Fix null reference when using default(PartitionKey)
[v4] Client Encryption: Refactor code to external project
[Internal] Query: Add code generator for CosmosNumbers for easy additions in the future.
Co-authored-by: Matias Quaranta <[email protected]>
…om/Azure/azure-cosmos-dotnet-v3 into users/jawilley/document/exceptions
/// </item> | ||
/// </list> | ||
/// </exception> | ||
/// <exception>https://aka.ms/cosmosdb-dot-net-exceptions#typed-api</exception> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simple URI might not get attention.
Existing annotation seems reasonable and we could leverage.
How about merge both of them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FabianMeiswinkel and @ealsur what are your thoughts?
The issue with the old format is it was duplicated in so many places that most of them were missing different scenarios. Trying to explain which exceptions the SDK retries on vs which ones they need to handle along with different exception scenarios seemed like to much to duplicate any every comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer the Uri approach - easier to get it right - and customers who look for this info will follow the link - customers who are neglecting exception info will neglect it whether it is in the comments or not
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, it helps maintaining a unified documentation store
Closing due to in-activity, pease feel free to re-open. |
Pull Request Template
Description
Add a new exception document that details what the different exception types are and what the normal status codes are. Updated all comments to reference new document.
Type of change
Please delete options that are not relevant.