-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Feature/storage/blob base client request validation #22136
Feature/storage/blob base client request validation #22136
Conversation
@@ -1132,6 +1132,12 @@ private void SetNameFieldsIfNull() | |||
|
|||
ResponseWithHeaders<Stream, BlobDownloadHeaders> response; | |||
|
|||
// All BlobRequestConditions are valid. |
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.
if this is the case, is this just here just in case of the future that there are conditions added that are invalid?
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.
Yep!
@@ -10,6 +10,7 @@ | |||
- Added support for OAuth copy sources for synchronous copy operations. | |||
- Added support for Parquet as an input format in BlockBlobClient.Query(). | |||
- Added optimization to unwrap encryption key once for DownloadTo and OpenRead when Client Side Encryption is enabled. | |||
- Added support for RequestConditions parameter validation. If a request condition is set for an API that doesn't support it, and Arguement Exception will be thrown. |
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.
we should mention compat switch in changelog.
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.
compat switch?
/azp run net - storage - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
No description provided.