{"push_id":637938103,"size":1,"distinct_size":1,"ref":"refs/heads/BrannonPart2","head":"27fbabdb07b18a02a6b844f64718ec6cf3af47a6","before":"7485efc060813817e4deacf70a5d7031081fc474","commits":[{"sha":"27fbabdb07b18a02a6b844f64718ec6cf3af47a6","author":{"email":"b8abbb9251072cdfd336331432bd50493c85befe@outlook.com","name":"againstgrizzly"},"message":"All collections made either List or Set\n\nIt’s good coding practice to code against the interface an not the\nimplementation.\n\nIt’s almost always preferable to code against the interface and not the\nimplementation. This way, if you need to change the implementation\nlater, it won’t break consumers who code against the interface - Matt\nBall\n\nReturning List will make it possible for users of your library to use\nanything that implements a List interface, while using an ArrayList\nwill force them to use an ArrayList.- ipvalic","distinct":true,"url":"https://api.github.com/repos/codemaster333/Project3SearchEngine/commits/27fbabdb07b18a02a6b844f64718ec6cf3af47a6"}]}