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
Hi @karrick (I'm hoping you are still around here)
I saw that you've strictly followed the Avro specification in order to develop/maintain this go module. About the JSON encoding, I've seen some complaining about the TextualFromNative() inserting types fields for union Avro types (i.e. #167 and #106). For what I've seen on the specification, these types fields should exist, because TextualFromNative?() use a JSON format.
My question is about NativeFromBinary(). I'm getting type fields in the interface{} returned from it. Shouldn't these types only be added for JSON encoding? The Native is a map (or interface{}) object in go, not a JSON, right?
If an example is required, there is one in the function description.
Hi @karrick (I'm hoping you are still around here)
I saw that you've strictly followed the Avro specification in order to develop/maintain this go module. About the JSON encoding, I've seen some complaining about the TextualFromNative() inserting types fields for union Avro types (i.e. #167 and #106). For what I've seen on the specification, these types fields should exist, because TextualFromNative?() use a JSON format.
My question is about NativeFromBinary(). I'm getting type fields in the
interface{}
returned from it. Shouldn't these types only be added for JSON encoding? TheNative
is a map (or interface{}) object in go, not a JSON, right?If an example is required, there is one in the function description.
The text was updated successfully, but these errors were encountered: