googlemaps / googlemaps/google-maps-services-python
places and places nearby need an optional fields parameter like places
- Linguagem predominante
- Python
- Estrelas
- 5k
- Forks
- 1.4k
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
Thanks for stopping by to let us know something could be better!
---
**PLEASE READ**
If you have a support contract with Google, please create an issue in the [support console](https://cloud.google.com/support/). This will ensure a timely response.
Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform [support resources page](https://developers.google.com/maps/support/).
If your bug or feature request is not related to this particular library, please visit the Google Maps Platform [issue trackers](https://developers.google.com/maps/support/#issue_tracker).
Check for answers on StackOverflow with the [google-maps](http://stackoverflow.com/questions/tagged/google-maps) tag.
---
**Is your feature request related to a problem? Please describe.**
I am frustrated the places and places_nearby function calls do not allow me to specify the fields I want returned like in the place function call.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
I would love an optional fields parameter to help me shorten the length of responses.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
https://github.com/googlemaps/google-maps-services-python/blob/master/googlemaps/places.py
Guia de contribuição
Direção de pesquisa
Open googlemaps/places.py and inspect the places and places_nearby entry points alongside the existing place call's fields handling. Done means both calls accept an optional fields parameter and use it to shorten responses as requested; verify the behavior against the linked implementation context.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- python
- Domínio
- api
- Tipo de issue
- Funcionalidade
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Estagnada
- Clareza
- Claramente especificada
- Facilidade para iniciantes
- 45/100