Don't parse notebook file

[hadim]

I am using the latest version.

I use the mkdocs-jupyter plugin so I have some ipynb files in my nav:

nav:
  - Examples:
      - dsdasda: examples/xxx.ipynb
      - dsdsd: examples/xxx.ipynb
      - dasdasd: examples/xxx.ipynb

It looks like mkdostrings try to parse those files because I have plenty of the following warnings:

WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[C]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[C]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[O]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[readonly]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[readonly]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[readonly]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[C]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[C]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[O]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[=C]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[=C]' 
WARNING -  mkdocstrings.plugin: examples/dsdsdsd.ipynb: Could not find cross-reference target '[=C]' 

Would that be possible to add an option to ignore those files? (it also slows down the doc building process because usually, those notebook files are quite large (JSON based).

[pawamoy]

Damn, sure, we should definitely add a way to ignore some files.

I think I'd like options to ignore both patterns in files, and pattersn in files names.

[pawamoy]

Moving this to autorefs as it's responsible for cross-references.

[johnslavik]

Can't reproduce. Maybe fixed by mkdocs-jupyter upstream? Please lmk about repro steps if you still encounter this.

[pawamoy]

I'll close as per @bswck's investigation and comment. We'll reopen if the initial issue is updated 🙂