The JSON result returned is valid but easy to work with programmatically. Most of the data returned has keys that are actually the values.
E
Electric violet Wombat
ISSUE: The JSON result returned is valid but NOT easy to work with programmatically. Most of the data returned has keys that are actually the values.
EXAMPLE (CURRENT):
{
"employee_count_by_month": {
"2010-01": 111106,
"2010-02": 111323
}
}
SUGGESTED FIX:
{
"employee_count_by_month": [
{"month:":"2010-01", "count": 111106},
{"month:":"2010-02", "count": 111323}
]
}
DETAILS: You can't deserialize the data back into objects under the current schema because the key is truly a value and therefore not finite.
CONS: Makes the file larger
IDEA: You probably can't change the schema since it's been published - but you could add a flag that allows the data to be returned structured as in the suggestions above.