Interface from Go to Vizceral json format found inconsistencies
adrianco opened this issue · comments
I just built a first rough pass at a go package that maps the vizceral format
https://github.com/adrianco/go-vizceral
I ran into an issue where "metadata" is sometimes "streaming": true, and sometimes "streaming": 1 in the example file, which causes an error when marshal/unmarshal from go. I edited a copy of the example file to use "streaming": 1 everywhere, but it would be better to fix upstream wherever this data was generated.
@adrianco Sounds like Go is having issues with the marshalling and unmarshalling and this is a Go specific problem, rather than a Vizceral problem as the metadata field is optional and the example file is valid JSON.
@jasonwr It does point out inconsistencies with how the backend was generating the data. It is a very valid issue to point out.
@adrianco Thank you for pointing this out! I have since fixed the backend data generation to be consistent and updated the the sample json in f125a2f. Please let me know if you find anything else.
@jrsquared @adrianco My apologies! Good catch! I do know that your example data is valid JSON.
Thanks for fixing this, I know that it is valid json, but when interfacing json to typed languages like Go it's much easier when the json types are consistent.