You can clone with
HTTPS or Subversion.
bump version to 0.2.1
If unexpected response code, exception should include diagnostic info
Bump version to 0.2.0
Fix "endearing" quirk where you can't build the gem unless you alread…
…y have the gem installed
support person lookup by site profile, for API v3.
Bump version to 0.1.7
URLencode email addresses before sending them to Rapleaf. Remove work…
…around for mistakenly diagnosed problem (thought Rapleaf rejected emails containing '+', they just required encoding).
Don't create a new NotFound exception class when there's a perfectly …
…good PersonEmailHashNotFound class.
Bump version to 0.1.6, update documentation
Default to API v3
Support Rapleaf person API v3
Work around Rapleaf's rejection of emails containing '+' by sending h…
…ashes for those emails instead.
Handle Rapleaf 404 response (happens when querying by a hash they don…
Allow passing hashes explicitly: e.g. person(:md5 => "abcabc")
Extract method for calculating person lookup API URL
remove Rapleaf::Base#abook - it's been empty and TODO for a year and …
Removed signing key info from .hoerc which removed it from gemspec.
Correct gem name and add git clone instructions.
Converted to using Hoe for gem management.
Version bump to 0.1.4
Minor require change
Touch gemspec to rebuild gem
Touching gemspec version to see if I can get GitHub to build a gem.
Require rubygems in example.
Touching file to force GitHub rebuild. Such a silly process.
Trying to see if I can get GitHub to actually build a gem...
Allow local install
Include example files in the gem.
Removed old comment.
Hopefully the RubyGem will build now on GitHub.
Added GitHub URL to README
Added first basic working copy of the Rapleaf lib