Skip to content
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

Merged
merged 7 commits into from
Jun 12, 2020

Conversation

j82w
Copy link
Contributor

@j82w j82w commented Jun 5, 2020

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.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Copy link

@github-actions github-actions bot left a 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.

@j82w j82w changed the title Documentation: Exception handling Documentation: Add exception handling document Jun 6, 2020
@github-actions github-actions bot dismissed their stale review June 6, 2020 00:09

All good!

/// </item>
/// </list>
/// </exception>
/// <exception>https://aka.ms/cosmosdb-dot-net-exceptions#typed-api</exception>
Copy link
Member

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?

Copy link
Contributor Author

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.

Copy link
Member

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

Copy link
Member

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

@j82w j82w merged commit ce1a9db into master Jun 12, 2020
@j82w j82w deleted the users/jawilley/document/exceptions branch June 12, 2020 11:32
@ghost
Copy link

ghost commented Dec 15, 2021

Closing due to in-activity, pease feel free to re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants