Recursively generate documentation for entire module without creating individual markdown files

We’d like to generate documentation for our entire module without generating a markdown file for each file. I assume this is possible, but I am having trouble doing it myself.

I have tried just adding ::: package-name to a file - which does document all contents - but it’s all in one file, which is not the ideal solution. Ideally, I’d like classes and files to be automatically placed in the sidebar.

I’m using mkdocstrings version 0.15.0. The contents of my mkdocs.yml file does not seem to be relevant.

[jmkd3v]

Take a look at #179 (comment) (not yet sure if the issue is duplicate or not)

While this does partially solve the problem, it’s not a solution if it can’t actually add the items to the nav. I assume I can write up a script that does this and then edits the nav in the mkdocs.yml file before building, but I was hoping for a more streamlined solution.

[oprypin]

Take a look at https://github.com/mkdocstrings/mkdocstrings/issues/179#issuecomment-784631904 (not yet sure if the issue is duplicate or not)