-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Click sub-command name renaming not detected #74
Comments
Yeah, this isn't something we currently support. I'm not sure how easy it would be to fix this since we don't fully evaluate the application. |
Ok. That makes sense and it guards against some side effects. |
Unfortunately not, no |
Hmm. |
the renamed names are lost in these lines: sphinx-click/sphinx_click/ext.py Lines 285 to 288 in aa0d5b7
prior to those lines, for a this issue is preventing me from using |
I'd welcome a pull request to fix this. Please include tests |
This adds auto-generated docs for the wsinfer cli. This commit also renames the subcommand cli function names, to account for click-contrib/sphinx-click#74
This adds auto-generated docs for the wsinfer cli. This commit also renames the subcommand cli function names, to account for click-contrib/sphinx-click#74
Hi, I'm using the most current version of Sphinx (3.4.2), Sphinx-Click (latest) and click (7.1.2).
My situation is like this:
main
(modulemodA.cli
in package packageA)modB.cli
in package packageB) I also have a CLI and import the groupmain
frommodA.cli
assubmain
submain
group to themodB.cli
command groups as a subcommand.If I now execute
packageB
I will see the subcommandsubmain
as possible choice. In the generated documentation it however will still appear asmain
(name frommodA.cli
I would suppose)Not sure if the example code can reproduce this or if it has to be separate packages (not just modules)...
I will then call the
modB.cli:main()
entry point.Documentation is dead simple:
The text was updated successfully, but these errors were encountered: