-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any type json marshaling. #170
Comments
It's just something we haven't gotten to yet. The text format supports Any messages; jsonpb just needs to be updated. |
If you can give me some hints as to where I should be hooking in, I'd be glad to try and tackle this problem, as it's something of great interest to me. ATM, I'm mildly confused as to wether I should be poking at marshalValue or marshalObject, as neither seem particularly well-suited for types that are actually objects, instead of primitives, at least in the WKT corner. Or am I to assume that this isn't exactly trivial in the current code layout, and that's why it's not been gotten to yet. |
I'll see if I can get it done today. |
I should have marshaling done later today. It was a bit trickier than the other well-known types. Unmarshaling is going to be harder again; that'll be a TODO for now. Is that going to be something important for you? |
Marshaling only will be fine for now. However has there been a tracking bug for me to follow for possible updates in the future? |
There isn't, but feel free to open one. |
It'd be nice if the Any type could be marshaled properly by jsonpb, as currently it ends up marshaling as a couple of strings, one of which being the base64-encoded value of the type.
I recognise this might not be an easy-to-do thing (I had forked to try and get it going, but couldn't find an obvious place for it. ) however it is still wanted, so at the very least this can be a tracking bug or similar.
The text was updated successfully, but these errors were encountered: