{"push_id":726668160,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"a433fe5f34c1b2edae1f89772d6d58a153815fdd","before":"a932b7147bad27e6d9ecf1e6eedce4d71266a372","commits":[{"sha":"e14c53595712eaad779ffba09c59d0c6c9a2e7c7","author":{"email":"9a57d87c89e9efe587859fa3f4177b0e0981f771@gmail.com","name":"Thomas Santana"},"message":"Added boolean selection on RHS of rules.","distinct":true,"url":"https://api.github.com/repos/nebulorum/bloom-spike/commits/e14c53595712eaad779ffba09c59d0c6c9a2e7c7"},{"sha":"a433fe5f34c1b2edae1f89772d6d58a153815fdd","author":{"email":"9a57d87c89e9efe587859fa3f4177b0e0981f771@gmail.com","name":"Thomas Santana"},"message":"Fixed bug in field lookup when collection and field have same name.\nThis was caused by using matching objects with same name and not the same object in pattern matching in entityWithName. Seems we need to use eq when testing the parent pair relation. Using == will cause matching on the wrong element of the FieldAccessor, causing a cycle on the data flow calculation. With object equality we do not have this issue.","distinct":true,"url":"https://api.github.com/repos/nebulorum/bloom-spike/commits/a433fe5f34c1b2edae1f89772d6d58a153815fdd"}]}