{"push_id":1219334753,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"cf03b9c54a7420f5e02cea12b5b2f916b4da150f","before":"54ff93874962e824d95829aa94740a125e1395b2","commits":[{"sha":"cf03b9c54a7420f5e02cea12b5b2f916b4da150f","author":{"name":"Dmitry Frank","email":"87db00780639216c5b5ba171ec0e787fd3edf64a@cesanta.com"},"message":"Improve json_walk API\n\nNow, for each composite type (objects and arrays) there are two token\ntypes: _START and _END. It is useful for `json_walk()` API, but kinda\nconfusing for scanf-based API: it's _END at which the value is\nconsidered, so, client code should use `JSON_TYPE_OBJECT_END` and\n`JSON_TYPE_ARRAY_END` instead of `JSON_TYPE_OBJECT` and `JSON_TYPE_ARRAY`.\n\nMaybe I should add something like:\n\n```\ndefine JSON_TYPE_OBJECT JSON_TYPE_OBJECT_END\ndefine JSON_TYPE_ARRAY JSON_TYPE_ARRAY_END\n```\n\nLet me know if I should.\n\nPUBLISHED_FROM=6587579d1f9ac24c89e733af957e5229187ba400","distinct":true,"url":"https://api.github.com/repos/cesanta/frozen/commits/cf03b9c54a7420f5e02cea12b5b2f916b4da150f"}]}
{"actor":{"display_login":"cesantabot"}}