I am not dismissing that these warnings should be able to be silenced. I'll handle that in the upcoming months.

That is great, thanks.

Yes, it's a bug in the plugin. It will be there regardless if you're able to silence all warnings.

I don't think that is the case. Plugin I use is mkdocs-macros that lets me, among other things, use python to create functions which I can use on md pages via jinja templates. This is the macro I wrote which creates this problem.

I have 3 files X.md, X.sql, X.txt, each in the same folder inside the docs folder. The md page describes a database table and X.sql contas DDL while X.txt contains data sample.

In main.py that macros plugin lets me use:

    @env.macro
    def inc( page, ext="sql", title="SQL" ):
        fileFullName = page.title + '.' + ext
        fileFullPath = page.file.abs_src_path.replace('.md',  f'.{ext}')

        try:
            with open(fileFullPath) as f:
                lines = f.read()
        except FileNotFoundError:
            return ''

        return f"""
## {title}
Download: [{fileFullName}](../{fileFullName})             <============ generates warnings
```{ext}
{lines}
```   `
"""

In X.md

#  X

...

{{ inc( page, 'sql', 'SQL') }}
{{ inc( page, 'txt', 'Data Example') }}

So this is mkdocs that warns me about this, not the plugin, so handling warning should help as far as I can see.

Uh oh!

Disable navigation warning #1888

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions