show base classes

[hamelsmu]

Still having an issue getting MdRenderer to show up properly. @machow do you think this bug still exists that you mentioned earlier. I was able to retrace all the steps and I think I understand the code base a bit better now, but I am not sure where to start debugging this specific issue.

I'll try to take a break from this and come back to it

[machow]

Still having an issue getting MdRenderer to show up properly.

Shoot -- I think it was likely a matter of me needing to document that options currently don't get combined together. So, if you set options at the top-level, and then set them in a section, only the ones in the section get applied.

I added some documentation to this PR of how options get applied, and how they can be combined using YAML merge keys. It's def fair game to raise whether or not they should get combined, though 😓.

Debugging Auto

Here's what I ran to confirm that show_bases at least worked for individual pieces of content

from quartodoc import Auto, blueprint, MdRenderer
obj = Auto(name = "quartodoc.tests.example_class.Child", show_bases=True)

MdRenderer().render(blueprint(obj))

# quartodoc.tests.example_class.Child { #quartodoc.tests.example_class.Child }

`tests.example_class.Child()`



Bases: `C`



## Methods

| Name | Description |
| --- | --- |
| [some_new_method](#quartodoc.tests.example_class.Child.some_new_method) | A new method |

### some_new_method { #quartodoc.tests.example_class.Child.some_new_method }

`tests.example_class.Child.some_new_method(self)`

A new method

Debugging yaml config

Here's the stripped down yaml config I used to get a minimal example

quartodoc:
  package: quartodoc
  options:
    show_bases: true
  sections:
    - options:
        dynamic: true
      contents:
        - name: MdRenderer

Updated docs