-
Notifications
You must be signed in to change notification settings - Fork 321
azure_core::Error & identity::Error #266
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
Conversation
rylev
left a 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.
Looks good to me. I obviously didn't look at every single file, but I believe I looked at all non-generated code.
| .map(|s| -> Result<LoginResponse, Error> { | ||
| Ok(serde_json::from_str::<LoginResponse>(&s)?) | ||
| })? | ||
| // TODO The HTTP status code should be checked to deserialize an error response. |
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.
Can we create an issue for this?
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.
This continues a refactor of error handling that started in #251. The biggest changes are:
azure_core::errors::AzureErrorrenamed toazure_core::Erroridentity::Error?is usable by consumers.trait azure_core::TokenCredentialremains the sametrait azure_identity::token_credentials::TokenCredentialis the same asazure_core::TokenCredential, but returns a specific error from the azure_identity crate