{"push_id":631489794,"size":1,"distinct_size":1,"ref":"refs/heads/patch-3","head":"c937623fba7544e3aa5aefac696ea5d49136f315","before":"f73593b00e3b2c927bb1a3236240cea5597166ec","commits":[{"sha":"c937623fba7544e3aa5aefac696ea5d49136f315","author":{"email":"0e02868158d22159fd2aa6729d859b8ae8f7fcfa@gmail.com","name":"Sterling Crispin"},"message":"Update Box3.js\n\nthe order in which  isIntersectionBox and containsPoint was checking for overlapping was to see if the object in question was NOT overlapping, then returning false if evaluating as true, and true if evaluating as false. That's really counter intuitive and confusing. I switched the less than or grater than signs and the false trues so that if the function evaluates as true, it returns true, if not it returns false. This should't change the way users interact with the function but it's much more intuitive source code.","distinct":true,"url":"https://api.github.com/repos/sterlingcrispin/three.js/commits/c937623fba7544e3aa5aefac696ea5d49136f315"}]}