- Mar 09, 2011
-
-
Alex Reisner authored
Update gemspec: summary, description, and files. Also add json gem dependency and update CHANGELOG and README with lots of new features!
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
-
- Mar 08, 2011
-
-
Alex Reisner authored
Does not seem like a significant gain to have the auto-assignment AND a custom block. In fact, it seems annoying to have to use a different method. So now, passing a block to geocoded_by or reverse_geocoded_by prevents any auto-assignment from happening.
-
Alex Reisner authored
Use 'geocode' instead of 'fetch_coordinates!'.
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
Should have been part of commit cbda51e8.
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
Detect this at the Lookup level (instead of the Rack::Request level, for example) and return the response we know Freegeoip.net will give.
-
Alex Reisner authored
-
Alex Reisner authored
This should have been part of commit 8cc460f9.
-
Alex Reisner authored
-
- Mar 07, 2011
-
-
Alex Reisner authored
Add geocode and reverse_geocode methods along with bang versions which can be used to skip auto-assignment of address or coordinates (specify a block that handles the Geocoder::Result instead).
-
Alex Reisner authored
Be sure to return nil.
-
Alex Reisner authored
If forward and reverse geocoding were both declared and options passed for both, only the options for the first were being set.
-
- Mar 06, 2011
-
-
Alex Reisner authored
-
Alex Reisner authored
Kill some old, unnecessary require statements.
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
-
- Mar 05, 2011
-
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
More than one result is very rare and it's not clear how one would evaluate the choices. If this is required in the future a new method can be added.
-
Alex Reisner authored
-
Alex Reisner authored
This fixes a scope problem: blocks are evaluated in the context in which they are declared so custom routines were being evaluated in the context of the class, not the object.
-
Alex Reisner authored
Don't take 'reverse' argument, instead figure it out by looking at what options were specified for the model. Also, don't raise exceptions on bad configuration (no longer possible to detect, wasn't that important).
-
Alex Reisner authored
city, country, country_code, postal_code
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
-
Alex Reisner authored
Should have been part of commit 29af848a.
-
Alex Reisner authored
Split result parsing into separate method.
-
- Mar 04, 2011
-
-
Alex Reisner authored
No longer necessary.
-
Alex Reisner authored
Use JSON (json gem) instead.
-
Alex Reisner authored
-