verdi327/walkscore — pull request #1 by kpullen (2012-08-23 09:12:51+00:00)
Title: Attempt to make Walkscore all shiny

This commit is a doozy, and I really should have broken it up into
many small chunks, but I was on a roll for a while. Here is a (probably
incomplete) list of changes I have made:

* The WalkscoreApi module is now named Walkscore
* The client object is now the locus of all interaction with the Walkscore
gem. A client object is created with an API key, and you get a location's
score by passing a latitude and longitude to #score_at
* The resulting object now returns most of the data sent back from Walkscore,
and even transforms some of the data. For example, updated (now updated_at)
used to return a string. Now it returns a Time object. All URIs now return
URI objects.
* The README has been updated with more information about Walkscore and their
branding requirements.
* All the tests were removed and redone, and now test for many more edge cases.
* The client raises different errors depending on what status Walkscore returns.
* The tests all use VCR to record network traffic and play it back, thus
avoiding any need for tests to communicate via the network.

Hopefully these changes are in line with your goals for the library. Please let me know if you need more information.