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
SetResponse contains repeated UpdateResult response = 2;; however, UpdateResult's fields timestamp and message (Error) fields are deprecated. Remaining two fields are to carry the path and Operation details, which are pretty much dependent on incoming SetRequest. These were making sense when each element was carrying the error information if there's any. Given this, should UpdateResult continue to be part of SetResponse? Or, should it also be considered to deprecate this as well? As the error reporting is part of the RPC return, this UpdateResult in response may not carry any useful information.
The text was updated successfully, but these errors were encountered:
SetResponse contains
repeated UpdateResult response = 2;
; however,UpdateResult
's fieldstimestamp
andmessage (Error)
fields are deprecated. Remaining two fields are to carry the path andOperation
details, which are pretty much dependent on incomingSetRequest
. These were making sense when each element was carrying the error information if there's any. Given this, shouldUpdateResult
continue to be part ofSetResponse
? Or, should it also be considered to deprecate this as well? As the error reporting is part of the RPC return, thisUpdateResult
inresponse
may not carry any useful information.The text was updated successfully, but these errors were encountered: