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
Is your feature request related to a problem? Please describe.
I noticed in my own code that I exposed an object coming from a sibling module in __all__.
I consider this bad practice, and would like a way to warn me if something like this is detected by Griffe.
Describe the solution you'd like
When visiting __all__ assignments or when expanding exports, check that exposed objects were either declared in this module, or in a submodule.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
…odule instead of the current module or a submodule is exported
Implemented as a DEBUG log for now, waiting for a logging configuration system.
Issue-249: #249
Related-to-PR-251: #251
Is your feature request related to a problem? Please describe.
I noticed in my own code that I exposed an object coming from a sibling module in
__all__
.I consider this bad practice, and would like a way to warn me if something like this is detected by Griffe.
Describe the solution you'd like
When visiting
__all__
assignments or when expanding exports, check that exposed objects were either declared in this module, or in a submodule.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: