{"push_id":1042126787,"size":1,"distinct_size":1,"ref":"refs/heads/mx-implicit-dependencies","head":"07b7681112a528241be88a29cc2e5447a48e7650","before":"6806e6be54d275f107ac0670b93c43440a43513a","commits":[{"sha":"07b7681112a528241be88a29cc2e5447a48e7650","author":{"email":"b1c1d8736f20db3fb6c1c66bb1455ed43909f0d8@melissaxie.com","name":"Melissa Xie"},"message":"Simplify how we specify dependencies in our classes and their specs\n\nEach class and their correspending unit specs should really only have to specify\ndependencies that are directly related to them without having to reach too far.\nFor example, the `EventFinder` spec should only have to require the file\ncontaining its class and nothing else that the class itself actually depends on,\nlike `Eventbrite::Event`.\n\nOn the other hand, we could also move some spec config over to the\n`spec_helper.rb` file and have `rails_helper` refer to it, so that that can be\ncentralized and shared across all tests.","distinct":true,"url":"https://api.github.com/repos/railsbridge-boston/railsbridgeboston_dot_org/commits/07b7681112a528241be88a29cc2e5447a48e7650"}]}