Make documentation linkage between api names easier to find/see

Abierto
  • ¿Algo no está bien?
#394 5 comentarios 0 reacciones 1 asignado Ver en GitHub

@amuramoto ya está trabajando en esto.

Desde el 27/1/2023.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

priority: p3 type: docs

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.

Lenguaje dominante
Python
Estrellas
5k
Forks
1.4k
Merge medio
5 h 9 min
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de googlemaps/google-maps-services-python

Todos los issues de googlemaps/google-maps-services-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.