-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Table: batch method does not validate Operations types #126
Milestone
Comments
joostdenijs
pushed a commit
to joostdenijs/azure-sdk-for-java
that referenced
this issue
Jan 18, 2013
Change the pom xml id references from azure->windowsazure fixes Azure#126
Closed by accident (commit referenced this id, but was for a different repo) |
low priority, close, will open if customer ask. |
gcheng
pushed a commit
to gcheng/azure-sdk-for-java
that referenced
this issue
Sep 6, 2013
forward integration
jianghaolu
pushed a commit
to jianghaolu/azure-sdk-for-java
that referenced
this issue
Apr 5, 2017
forward integration
navalev
pushed a commit
to navalev/azure-sdk-for-java
that referenced
this issue
Dec 24, 2019
…zure#126) * merging DnsSuffix and servicename * incorporate CR comments * fix merge issues * fix UTs * cr comments * cr comments * fix failing UTs after merge issues * fix merge issues
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Moved from private repository
The Operation type can be implemented by the user, then plugged into the BatchOperations.getOperations list and passed to the batch method. However, the code (increateBatchRequestBody and parseBatchResponse) only acts on the operations when they are instances of the prefefined *Operation types, other types just fall out the end of the if..else if... chain.
It would be good to close those if...else if... chains with a trailing else { throw "Unexpected input blah" }. This would also help out of the user inserts a null value in the list.
The text was updated successfully, but these errors were encountered: