{"push_id":2440406297,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b99482d49cecae095fe1198c912f47f11f0d06af","before":"c1d0c846239a0183ba31c48715ec9e925179c58c","commits":[{"sha":"b99482d49cecae095fe1198c912f47f11f0d06af","author":{"name":"Nathan Hunzaker","email":"e0471ad47e60c23b7d63ddeadfb971f099e9193c@gmail.com"},"message":"[micromanage] Add schemas\n\nThis commit adds an initial draft of schemas. If an entity is created\nwithout a schema, it fails. Additionally, if a property does not match\nthe schema, it fails.\n\nI like the strictness, but I also know that it would be a bummer for\nan API to change a string or number field, or decide to return null. I\nstill need to figure out the best approach for that.\n\nOne idea is to allow it, with an option to send warnings about schema\nmismatches in a backchannel. You'd get an alert about the issue, but a\nuser wouldn't see an error.\n\nThis is probably okay for numbers, strings, and booleans. What about\ndates?","distinct":true,"url":"https://api.github.com/repos/vigetlabs/microcosm/commits/b99482d49cecae095fe1198c912f47f11f0d06af"}]}
{"actor":{"display_login":"nhunzaker"}}