-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make documentation linkage between api names easier to find/see #394
Comments
This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you! |
Closing this. Please reopen if you believe it should be addressed. Thank you for your contribution. |
Reopening as valid. We could edit the description of each subclass of Client (e.g. Client.directions()) to include a link to the corresponding documentation on developers.google.com (e.g. Directions API documentation). For directions, the description is defined toward the beginning of directions.py. |
This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you! |
Still valid! |
First off, really effective wrapper and complete on all the Google APIs. No complaints from my usage so far.
This is very trivial, but for complete newbies like me, might be helpful. Remembering that Google has a lot to say about it's APIs that might not be captured in this documentation (and shouldn't be), e.g. if you include a region code in a Places request, the country name is excluded from formatted address. So . . .
Perhaps in documentation and/or code base doc strings, add reference to Google names for API? For instance, took me a long time to work through that "places" is the same as "textsearch" because "textsearch" doesn't appear in the code. A formatted print string separates "text" and "search", so references on repo pretty sparse.
Small idea. No big deal of course, but thought I'd try to contribute something back.
The text was updated successfully, but these errors were encountered: