{"push_id":1042049350,"size":1,"distinct_size":1,"ref":"refs/heads/handle-optional-fields-in-record","head":"cf83c76eef022638f066016eb6ae6b40f4058356","before":"9e93675def523fdfeef633ae6aed6b3feecd1348","commits":[{"sha":"cf83c76eef022638f066016eb6ae6b40f4058356","author":{"email":"fbb1b7feb933e9e2b29da320b1cb546622364fab@twilio.com","name":"Scott Reynolds"},"message":"Handle Optional Values within Records\n\nSummary:\nThis change allows for the use of optional fields, especially optional\nstrings within a record. Prior to the change the only null check on\nvalue is in the public toConnectData method. This isn't sufficient when\nhandling Avro Records. It is common to have a Record that has optional\ntypes within it.","distinct":true,"url":"https://api.github.com/repos/SupermanScott/schema-registry/commits/cf83c76eef022638f066016eb6ae6b40f4058356"}]}