This captures too many possible errors within the chain of methods which follow - better for this to error loudly
Prefer self.class.to_s over a stringified class name - that way if the class name changes, we don't have to update this
Added response json column to places - this is where api responses get stored
Updated user spec to include other default field/validation shoulda matchers, as well as to spec out exactly which methods should be tested
Added foursquare account spec
Use specific version of the foursquare gem
These methods should reside directly on the user class - not inside the weights module
Added attr_accessible for new places fields (response, source, meta)
Improved omniauth callbacks controller spec by adding foursquare specs, and also stubbing out responses on the account classes so that we don't actually make the API requests necessary to create data. We're really just interested in the relationship getting attached to the user
Disabled sign up fields
Moved has_? helpers to user account and added foursquare relationship
Use time.at instead of date.parse for finding the created at time for a foursquare account - the api uses unix epoch time
Spec out the process for consuming foursquare data