Issue with type hints in public API's
- 主要言語
- Python
- スター
- 415
- フォーク
- 50
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
There are some exposed functions, such as `create_async_client` and `create_client` whose type signature has some hints which are considered mistakes from many tools:
```python
def create_client(
dsn=None,
*,
max_concurrency=None,
host: str = None,
port: int = None,
credentials: str = None,
credentials_file: str = None,
user: str = None,
password: str = None,
secret_key: str = None,
database: str = None,
branch: str = None,
tls_ca: str = None,
tls_ca_file: str = None,
tls_security: str = None,
wait_until_available: int = 30,
timeout: int = 10,
):
```
A type which is not `T | None` cannot be assigned `None`, which causes this flurry of lints:

All public API's of the client should conform to strict typing in python to avoid consumers of the client to have to hack around their linting & LSP tooling.
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
Start with the public create_client and create_async_client entry points named in the issue, then identify the other exposed client APIs with similar optional parameters. Check their signatures with strict typing and linting tools; done means public APIs no longer report errors for parameters that default to None.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- python
- 領域
- api
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100