Open yav opened 2 months ago
I think it only makes sense to recurse the import tree in the trivial examples. Often we'd have modules being defined because they are being used in multiple places. We could avoid rechecking this modules multiple times with caching, but that seems like working around bad design with a speed-hack. For a project with multiple top-level leaf modules you'd already need to manually enumerate what those top-level modules are. It seems more principled to have a list of the modules you that want to check which includes those that might be imported by other modules.
At the moment we don't run doc-strings on imported modules, but perhaps we should? Here's an example:
"B"
Running
check-docstrings
after loadingA
doesn't do anything.