You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if this plugin could support a reporting scope of project, which typechecks all files in the current project (defined as the first directory in the tree with a pyproject.toml file).
We have a large monorepo where:
file scope is not useful as we need cross-file type checking
workspace scope is too broad, making type checking slow, and requiring the entire repo to be type-checkable (sometimes we files that will cause mypy to throw, such as a missing __init__.py file)
I'm not sure if mypy itself supports this kind of scoping, but if not, perhaps this plugin could detect the current project and pass that in as the directory to the mypy command i.e. python -m mypy /path/to/project.
At the same time, it is important that mypy config is respected from the root of the workspace. In monorepos, we tend to have a root pyproject.toml that defines mypy config, and it would be great to respect that.
The text was updated successfully, but these errors were encountered:
Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.
It would be great if this plugin could support a reporting scope of
project
, which typechecks all files in the current project (defined as the first directory in the tree with apyproject.toml
file).We have a large monorepo where:
file
scope is not useful as we need cross-file type checkingworkspace
scope is too broad, making type checking slow, and requiring the entire repo to be type-checkable (sometimes we files that will cause mypy to throw, such as a missing__init__.py
file)I'm not sure if mypy itself supports this kind of scoping, but if not, perhaps this plugin could detect the current project and pass that in as the directory to the mypy command i.e.
python -m mypy /path/to/project
.At the same time, it is important that mypy config is respected from the root of the workspace. In monorepos, we tend to have a root
pyproject.toml
that defines mypy config, and it would be great to respect that.The text was updated successfully, but these errors were encountered: