bazel-contrib / bazel-contrib/rules_mypy
Add mypy_test rule
- Dominant language
- Starlark
- Stars
- 12
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Depending on your project, you may not want to run lints like this as an aspect, since it potentially impacts developer's tight loop iterating on some python. I think it would be nice if this ruleset also provided a test rule that could be used to run mypy. I imagine it would be possible to still use aspects from that test to share the mypy cache with deps, but I haven't tried yet.
Contributor guide
Research direction
Start by reading the existing mypy aspect and the repository's Bazel rule and test patterns. Determine how a test rule should run mypy without forcing aspect-based linting, and whether sharing the mypy cache with dependencies is feasible; done means the ruleset exposes a usable test rule with documented behavior and passing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100