Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
auto generate command line docs for CLI using typer command line tool.
This is loosely based on the code from https://github.com/syn54x/mkdocs-typer2
I tried both the existing
mkdocs-typerandmkdocs-typer2pip packages, but couldn't get either to work. The first one hasn't been updated for 3 years and I couldn't get it to generate anything.mkdocs-typer2hooked / tried to generate, but failed internally trying to update the html tree withParseError: mismatched tag: line 449, column 3. Looking at the sourcecode I saw it used thetypercommand line tool to generate markdown and then generate html from it. I think the error is either in the generated HTML or because of the way its tryin to hook it into our material theme.So instead I just added a script like the other docs generation scripts we have and write the markdown directly
IT looks like this when renderd:

Type of change
New reference docs for CLI interface
How has this change been tested, please provide a testcase or example of how you tested the change?
locally running the script and
mkdocs serveAny specific deployment considerations
docs only
Docs
auto generates cli interace docs