Make documentation linkage between api names easier to find/see

未關閉
  • 哪裡不對？
#394 5 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@amuramoto 已經在處理了。

開始於 2023年1月27日。

評估

這個 Issue 還沒有評估資料。

描述

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.

主要語言
Python
星號
5k
分支
1.4k
平均合併
5 小時 9 分鐘
30 天內合併 PR
1

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

googlemaps/google-maps-services-python 的其他 Issue

查看 googlemaps/google-maps-services-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。