Thanks Luke! Chad Killingsworth
On Nov 10, 5:18 pm, Luke Mahé <[email protected]> wrote: > I've filed a internal issue about this to get the documentation cleared up. > > Thanks > > -- Luke > > > > > > > > On Thu, Nov 11, 2010 at 10:13 AM, Robert Poor <[email protected]> wrote: > > On Wed, Nov 10, 2010 at 12:59, Chad Killingsworth < > > [email protected]> wrote: > > >> I was pretty sure that the issue came from the misleading JSON > > > description. It badly needs updated. > > >> [snip] > > > The best way is to file an issue in the issue tracker. Just specify > > > that it is documentation related. > > >> Chad Killingsworth > > > Chad: thanks for the confirmation. I've dug around a bit but haven't > > found the issue tracker page for Maps/JS. Can you give me a pointer? TIA. > > > - ff > > > [P.S.: I've embraced the Path of Right Thinking and I'm now only accessing > > fields from the GeocoderResult via published methods. My life is much > > better now.] > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Maps JavaScript API v3" group. > > To post to this group, send email to > > [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-maps-js-api-v3%2B > > [email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-maps-js-api-v3?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
