{"push_id":689615909,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"dc78cf3aae236cc0f15f5b0fec116fdd55291493","before":"3a32964de4a2dac04a85c17de5f06c7fc7445883","commits":[{"sha":"dc78cf3aae236cc0f15f5b0fec116fdd55291493","author":{"email":"a35324c0444547237787fe53deb53379996a1928@gmail.com","name":"C.D. Clark III"},"message":"fixed fail_fast behavior for typ lists\n\nif a type is specified as a list, then the data should be validated\nagainst each element in the list and be considered valid if item\nsucceeds. the validate_type function does this by catching exceptions\nwith a try/except block until one schema validates.\n\nhowever, if fast_fail is turned off, then exceptions are not thrown\nimmediatly, they are instead placed in a list to be thrown later. this\ncaused the loop through possible schemas to exit after the first schema,\neven if it was not valide. however, the first schema would still put an\nerror in the _errors list if it was not valid.\n\nso, if the first schema raised an exception, its exception would be\nplaced in the esception list and the types loop would not catch it,\nexiting immediatly. then, even if a valid schema did exist at some point\nlater in the list, the validate function would report an error.\n\nthis fix monitors the _errors list to handle the above situation\ncorrectly.","distinct":true,"url":"https://api.github.com/repos/CD3/validictory/commits/dc78cf3aae236cc0f15f5b0fec116fdd55291493"}]}