Situationally disable extensions

[multimeric]

I'm using the excellent griffe_fieldz extension.

However in some cases I want to disable the dataclass handling. In my mkdocs.yml I have:

plugins:
- mkdocstrings:
    default_handler: python
    handlers:
      python:
        options:
          extensions:
          - griffe_fieldz:
              include_inherited: true

However, in the markdown file, even if I set the extensions list to empty, it doesn't get disabled:

::: lls_core.writers.Writer
    options:
        extensions: []

Any ideas how I might do this?

[pawamoy]

There are two obstacles to this:

1. when mkdocstrings encounters ::: lls_core.writers.Writer, it has probably already loaded it, because it loads entire packages at once at the first identifier. It means that it's too late for options that impact the collection of data, such as extensions.
2. some extensions themselves run on entire packages (using the on_package_loaded extension hook) because they must support inheritance/else, and for inheritance/else to work we need the whole package to be loaded. They will then apply their transformations recursively by descending into the objects tree. Once again, here it's too late to prevent the transformations for just lls_core.writers.Writer.

The solution to this must come from the extension itself. You could ask that it supports configuration options to exclude some objects from being processed. Depending on the complexity of what users of the extension need, we could consider adding the concept of "sub-extensions" to Griffe, so that extensions themselves can be hooked on too, with custom events. See #315.