Issue 2: "enum GoogleStatusCode" completeness
Status:  Fixed
Owner: ----
Closed:  May 2010
Reported by exi.m...@gmail.com, Jun 3, 2008
Not really a 'defect' but I couldn't open an issue as any other type... ?


Anyway, since we're implementing "enum GoogleStatusCode"... Why don't we
have all possible situations... ? I could extend the current list to:


    public enum GoogleStatusCode
    {
        Success = 200,
        BadRequest = 400,
        ServerError = 500,
        MissingAddress = 601,
        UnknownAddress = 602,
        UnavailableAddress = 603,
        BadKey = 610,
        TooManyQueries =620
    }

Personally, I'm getting my application to throttle if we find a 620... ;)
Jul 16, 2008
Project Member #1 chadl...@gmail.com
Sure, could you submit a patch?
Nov 10, 2009
#2 shaun%go...@gtempaccount.com
This patch fixes the following items:

1.  Issue 2  and  Issue 8 
2. Adds "FormattedAddress" property to Core.Address.
3. Adds an out param for GeoCode to the three geocoders that will return the status 
code from the server. There is an overload that will ignore the status code so it 
doesnt break any code.
Nov 10, 2009
#4 shaun%go...@gtempaccount.com
Good lord, it would help if I could update the correct file. SORRY EVERYONE!
StatusAndAddress.patch
17.1 KB   View   Download
May 22, 2010
#5 google%g...@gtempaccount.com
It doesnt look like you ever comitted this patch. Here it is again for just the 
GoogleStatusCode.cs file.
GoogleStatusCode.patch
418 bytes   View   Download
May 24, 2010
Project Member #6 chadl...@gmail.com
Thanks, applied in r44.
Status: Fixed
Oct 16, 2010
#7 johnriss...@gmail.com
I'm not seeing this change in the latest download version.