Removes LongRunningOperationsManager and LongRunningOperationsTrait in favor of a callback for longrunning operations which casts protos to objects depending on their type
TBD:
can we remove the longRunningOperation methods on the handwritten classes in favor of using the existing list*Operations methods?
What is the appropriate behavior when resumeOperation is called on a database for an instance operation?
Other thoughts:
Add a MessageActiveRecordInterface which includes a method fromMessage(Message $message). This would allow the OperationResponse to call this method in order to "hydrate" the protobuf object
Removes
LongRunningOperationsManagerandLongRunningOperationsTraitin favor of a callback for longrunning operations which casts protos to objects depending on their typeTBD:
longRunningOperationmethods on the handwritten classes in favor of using the existinglist*Operationsmethods?resumeOperationis called on a database for an instance operation?Other thoughts:
MessageActiveRecordInterfacewhich includes a methodfromMessage(Message $message). This would allow theOperationResponseto call this method in order to "hydrate" the protobuf object