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.
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.