Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[TechDocs] Support all mkdocs CLI options in techdocs-cli
See original GitHub issueFeature Suggestion
mkdocs supports a number of additional command line options, only some of which are supported by the techdocs-cli.
Instead of adding these one-by-one to the techdocs-cli, @iamEAP suggested that we just support all mkdocs CLI options in the techdocs-cli.
Possible Implementation
Commander (the library used in the techdocs-cli to parse CLI options) already supports the common -- syntax, to indicate the end of arguments that should be processed and the start or arguments that should be passed-through in some manner. This is enabled by default, it should just be a matter of passing these through to the underlying code as required.
Context
Specifically, as per #10604, I’d like to be able to use the --strict flag of mkdocs build
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I would still like to see this happen. We have currently a wrapper CLI around techdocs-cli that does some additional features that are not supported now. Supporting add
mkdocsflags would be a step towards us being able to deprecate our custom CLI. I might take a stab at this at some point, but not sure when I’ll be able to get to it.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.