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
We're using protobuf 2 to pass messages python <-> scala. I need to pass flexible nested dictionaries from python and their integer values need to stay integers, so struct won't work.
I see you have good reasons you can't add int to Struct Values. But what if you added a new type instead? (Porting my comment over.) E.g. StructWithInt, which would prioritize supporting int to the exclusion of whichever other constraints are in the way.
Thanks for considering. Would be excited to migrate away from passing my proto message as the string, json.dumps(dict).
The text was updated successfully, but these errors were encountered:
generally speaking, we avoiding adding new "well known types" they tend to have a fairly high long term maintenance cost for us. I recommend creating the type you need local toyour particular project.
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment.
This issue is labeled inactive because the last activity was over 90 days ago.
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please reopen it.
This issue was closed and archived because there has been no new activity in the 14 days since the inactive label was added.
We're using protobuf 2 to pass messages python <-> scala. I need to pass flexible nested dictionaries from python and their integer values need to stay integers, so struct won't work.
I see you have good reasons you can't add int to Struct Values. But what if you added a new type instead? (Porting my comment over.) E.g. StructWithInt, which would prioritize supporting int to the exclusion of whichever other constraints are in the way.
Thanks for considering. Would be excited to migrate away from passing my proto message as the string,
json.dumps(dict)
.The text was updated successfully, but these errors were encountered: