Few issues regarding the documentation

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
45/100
Issue 類型
文件
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
python
領域
documentation

研究方向

Start with doc/source/glossary.rst, then check the CORS and bucket lifecycle mentions at doc/source/tutorial.rst line 102 and b2sdk/api.py lines 194-195. Fix the dead sync.html link in doc/source/quick_start.rst line 77, then review the toctree in doc/source/api_reference.rst lines 44-66 and the REALM_URLS docstring in b2sdk/account_info/abstract.py lines 33-37. Done when each listed item is addressed or explicitly declined by a maintainer, since the thread has no replies.

由索引模型根據 Issue 內容生成。

描述

enhancement good first issue

Few remarks regarding the documentation were put into the git repository under:

  • doc/source/missing.txt
  • doc/source/remarks.txt

These files were removed in #178 and all issues from there are moved here.

doc/source/missing.txt:

Missing	

1. Missing explanation	
In 	
doc/source/tutorial.rst 	
    line 102 	
AND in 	
b2sdk/api.py 	
    line 194 	
there are mentions of "CORS rules" which are not explained anywhere.	
Nothing in doc/source/glossary.rst either. 	
Proposed fix: add to glossary, if possible, add to on-hover	

2. Missing explanation	
In 	
doc/source/tutorial.rst 	
    line 102	
AND in 	
b2sdk/api.py 	
    line 195	
there are mentions of "bucket lifecycle rules" which are not explained anywhere.	
Nothing in doc/source/glossary.rst either.	
Proposed fix: add to glossary, if possible, add to on-hover	

3. Dead link	
doc/source/quick_start.rst	
    line 77:	
"""	
    To learn more about sync, see `Sync <sync.html>`_.	
"""

doc/source/remarks.txt:

4.	
I cannot find these in code, but some of the elements of .. toctree:: in doc\source\api_reference.rst - lines 44-66 - do not have any titles (the fact that some of the others have them non-descriptive or non-helpful is another matter entirely).	
    api/internal/utils                      - b2sdk.utils	
    api/internal/cache                      - b2sdk.cache	
    api/internal/sync/action                - b2sdk.sync.action	
    api/internal/sync/exception             - b2sdk.sync.exception	
    api/internal/sync/file                  - b2sdk.sync.file	
    api/internal/sync/folder                - b2sdk.sync.folder	
    api/internal/sync/folder_parser         - b2sdk.sync.folder_parser	
    api/internal/sync/policy                - b2sdk.sync.policy	
    api/internal/sync/policy_manager        - b2sdk.sync.policy_manager	
    api/internal/sync/scan_policies         - b2sdk.sync.scan_policies	
    api/internal/sync/sync                  - b2sdk.sync.sync	
    api/internal/transferer/file_metadata   - b2sdk.transferer.file_metadata	
    api/internal/upload_source              - b2sdk.upload_source	


5.	
Dicts get squashed and much less convenient to read/copy from. E.g.:	
b2sdk\account_info\abstract.py, lines 33-37:	
"""	
    REALM_URLS = {	
        'production': 'https://api.backblazeb2.com',	
        'dev': 'http://api.backblazeb2.xyz:8180',	
        'staging': 'https://api.backblaze.net',	
    }	
"""	

while in the docs it looks like this:	
"""	
REALM_URLS = {'dev': 'http://api.backblazeb2.xyz:8180', 'production': 'https://api.backblazeb2.com', 'staging':	
'https://api.backblaze.net'}	
"""
主要語言
Python
星號
214
分支
68
平均合併
51 分鐘
30 天內合併 PR
6

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

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

Backblaze/b2-sdk-python 的其他 Issue

查看 Backblaze/b2-sdk-python 的全部 Issue

相似的 Issue

更多 Python Issue

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

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