Protobuf Fields - Deprecating a parameter as google.protobuf.Any instead of reserved
Question
Due to a circular dependency issue. We needed deprecate and reserved a parameter foo . However, we also want to continue supplanting that parameter on older versions of our App for foo .
Instead of making a reserved parameter: Is it okay to return it as a google.protobuf.Any with no repercussions?
1 answers
solution1
0 2019-07-16 01:08:53
No you shouldn't. This is a breaking contract that compromised several platforms. The best way is to create new files subverting it.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
How to iterate recursively over Protobuf Python message to find all field
What is the relation of protobuf message field id and field order?
How to set the `fields` parameter in the Google Drive GoogleAPIs v3 in Dart?
Google Form - not filled fields
Why does LinqPad create Fields instead of Properties?
Null nested fields in Google BigQuery
Why ever use fields instead of properties?
C# constructor initializing properties instead of fields?
Using array fields instead of massive number of objects
google app maker link fields of related records
Related Tags