{"push_id":665978932,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a3a690a7c3d344d1c1e4f424706593f27ca6ee0a","before":"dde6539b6974c98df20ea585cc285d48e9fc506e","commits":[{"sha":"a3a690a7c3d344d1c1e4f424706593f27ca6ee0a","author":{"email":"f2dd230c83b0bf8a7ab6867a3f65b67e7762f785@yahoo.com","name":"Aleksi Sapon"},"message":"Move Extent#contains(Location) to Location\n\nThe problem was that an extent might have multiple different data\nbounds, for example biomes and blocks. There is no guarantee that these\nhave the same size. This made the method unclear: what must the extent\ncontain from the location for it to be contained? The block, the biome,\nboth? In other words, if the location has a biome in the extent, but\nnot a block, is it contained in the extent?\n\nInstead, this adds methods to Location to check if it has a biome or a\nblock at its position. A method was also added to check if the location\nis in a given extent. This solves the issue described above by\nseparating the different data types.","distinct":true,"url":"https://api.github.com/repos/SpongePowered/SpongeAPI/commits/a3a690a7c3d344d1c1e4f424706593f27ca6ee0a"}]}