This issue is part of a Codex global repository code scan.
The Pyright configuration only includes top-level dpdata/*.py files. Most implementation code lives in nested packages under dpdata/formats, dpdata/plugins, and dpdata/md, so the type-check workflow has limited coverage of the format/plugin code paths where most parsers and writers live.
Affected config:
|
[tool.pyright] |
|
include = [ |
|
"dpdata/*.py", |
|
] |
Current configuration:
[tool.pyright]
include = [
"dpdata/*.py",
]
Repository shape from git ls-files dpdata '*.py' shows many nested modules outside this include pattern, including all parser/writer modules under dpdata/formats and registry modules under dpdata/plugins.
Suggested improvement: expand Pyright coverage to include nested package modules, or explicitly document why nested format/plugin modules are excluded.
This issue is part of a Codex global repository code scan.
The Pyright configuration only includes top-level
dpdata/*.pyfiles. Most implementation code lives in nested packages underdpdata/formats,dpdata/plugins, anddpdata/md, so the type-check workflow has limited coverage of the format/plugin code paths where most parsers and writers live.Affected config:
dpdata/pyproject.toml
Lines 131 to 134 in a7a50bf
Current configuration:
Repository shape from
git ls-files dpdata '*.py'shows many nested modules outside this include pattern, including all parser/writer modules underdpdata/formatsand registry modules underdpdata/plugins.Suggested improvement: expand Pyright coverage to include nested package modules, or explicitly document why nested format/plugin modules are excluded.