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
bugThis issue requires a change to an existing behavior in the product in order to be resolved.ClientThis issue points to a problem in the data-plane of the library.DocsStorageStorage Service (Queues, Blobs, Files)
I am also confused that, why we are declaring the StorageError struct itself as an error, but returning a pointer in handleError? Why not just declare the *StorageError as error and pass this pointer around?
What did you expect or want to happen?
We should update the doc (but IMO updating the error interface for StorageError is better) to:
varstgErr*StorageErroriferrors.As(err, &stgErr) { // We know this error is service-specificswitchstgErr.ErrorCode {
caseStorageErrorCodeContainerAlreadyExists:
RickWinter
added
Client
This issue points to a problem in the data-plane of the library.
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
labels
Jan 26, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugThis issue requires a change to an existing behavior in the product in order to be resolved.ClientThis issue points to a problem in the data-plane of the library.DocsStorageStorage Service (Queues, Blobs, Files)
Bug Report
.../sdk/storage/azblob
main
go version
:go version go1.17.3 darwin/amd64
In zt_examples_test, the doc states that we can extract the
StorageError
from response as:azure-sdk-for-go/sdk/storage/azblob/zt_examples_test.go
Lines 183 to 187 in 916bcb2
However, this is not valid in current implementation, since we are returning the
StorageError
with pointer value inhandleError
:azure-sdk-for-go/sdk/storage/azblob/zc_storage_error.go
Lines 62 to 65 in 916bcb2
I am also confused that, why we are declaring the
StorageError
struct itself as an error, but returning a pointer inhandleError
? Why not just declare the*StorageError
as error and pass this pointer around?We should update the doc (but IMO updating the error interface for
StorageError
is better) to:The text was updated successfully, but these errors were encountered: