But it doesn't look like the generated docs followed the import properly and exposed the GameObject at the root of my package. Am I missing some options? Sorry, I'm struggling to understand exactly what's possible here!
Describe the solution you'd like
I would like my package documentation to include the classes I exposed using __all__ in __init__.py files. I tried updating the processor configs and I can get the class name to show up but it does not seem to have any of the documentation.
Describe alternatives you've considered
Not sure what alternatives I have now. I can do this with Sphinx but I really hate that Sphinx executes all of your code so this project seemed pretty great!
Hey @Zeelot , I'm sure that technically it is possible as long as __all__ can be evaluated using ast.literal_eval(). :) I might look into that in a bit.
Is your feature request related to a problem? Please describe.
I keep all of my class implementations in private modules (python files starting with
_
). I export a public API using the__init__.py
file like this:But it doesn't look like the generated docs followed the import properly and exposed the
GameObject
at the root of my package. Am I missing some options? Sorry, I'm struggling to understand exactly what's possible here!Describe the solution you'd like
I would like my package documentation to include the classes I exposed using
__all__
in__init__.py
files. I tried updating the processor configs and I can get the class name to show up but it does not seem to have any of the documentation.Describe alternatives you've considered
Not sure what alternatives I have now. I can do this with Sphinx but I really hate that Sphinx executes all of your code so this project seemed pretty great!
Additional context
Thanks for all the work!