show_source option from mkdocstrings breaks when mkdocs-click is enabled

Hi, first of all thanks for your work on this project!

I’m opening this issue because I’ve encountered a conflict between mkdocs-click and the show_source option from the mkdocstrings plugin.

When I enable mkdocs-click under markdown_extensions, the show_source: true option from mkdocstrings seems to stop working — the source code no longer appear.

Here’s a simplified version of my configuration:

markdown_extensions:
  - pymdownx.highlight:
      anchor_linenums: true
      line_spans: __span
      pygments_lang_class: true
  - pymdownx.inlinehilite
  - pymdownx.snippets
  - pymdownx.superfences
  - admonition
  - pymdownx.details
  - attr_list
  # - mkdocs-click  <-- enabling this causes the issue

plugins:
  - search
  - mkdocstrings:
      handlers:
        python:
          paths: [<app>]
          options:
            show_source: true

I’d like to be able to decide whether to show the source or not, but currently enabling mkdocs-click removes that choice — the source is simply not shown.

To help illustrate the problem, I’ve attached two screenshots:

• One with mkdocs-click enabled (no source code visible)
• One without it (source code link is visible as expected)

Let me know if I can provide more details or help debug this further.

Thanks again!

mkdocs-click enabled and show_source: true

mkdocs-click disabled and show_source: true

[pawamoy]

What are you trying to achieve exactly? And can you show the actual Markdown contents?

If you document your CLI with

::: mkdocs-click
    :module: app.cli

...then this will be handled by mkdocs-click, not mkdocstrings, so mkdocstrings options (show_source or any other) won't apply.

Thank you so much for your reply!

I opened this issue because, using mkdocs-click, I can't display the command's source code in the documentation.

Here's the .md file I'm using:

# title title title

text text text text text text text text

::: mkdocs-click
    :module: <app>.cli
    :command: cli
    :prog_name: <app>
    :depth: 1
    :list_subcommands: true
    :style: table

What I'd like is a "hybrid" solution:

• Use mkdocs-click to automatically generate the command's documentation (great!);
• But also display the command's source code, as if I weren't using mkdocs-click.

Is this hybrid mode already supported, and maybe I just missed it?
Or is there a workaround to achieve this?

[pawamoy]

mkdocs-click and mkdocstrings are two distinct plugins, so it won't be possible to merge their logic easily. You could show the source of any Python object with https://pawamoy.github.io/markdown-exec/ and an executed code block like this:

```python exec="1" result="python"
import inspect
from your_app.cli import your_command
print(inspect.getsource(your_command))
```