Support default values for pydantic fields about pytkdocs

[pawamoy]

Yes, there is, but it requires a complete refactor of pytkdocs, which I'm working on. Finding the right architecture and data structures will take some time 🙂

I'm currently thinking about the possibility of serializing objects from "unknown" categories (not a module, class, function, method, property or builtin value), and providing custom templates in mkdocstrings (and/or a way for users to provide their own templates) to render them nicely in the docs.

[camold]

Great to hear this feature is planned for version 0.11. Would be very useful to avoid redundancy in the docstrings (we currently have to state the default values in the docstring).
Just as a note, pydantic also allows for constraints, e.g. Field(1, ge=0, le=2) for the definition of an attribute with values between 0 and 2. These constraints do not seem to show up in __fields__ or __field_defaults__ though. So I guess there is no hope of having them included in the docs as well?

[pawamoy]

When I added support for Attributes section, I forgot about Pydantic attributes, and told myself "attributes don't have defaults" 😅

[theoqian]

Same issue with attributes in class based on dataclass.

[pawamoy]

This won't be implemented here (unless someone sends a PR), but rather in Griffe, as an extension. Feel free to open a feature request there (it's already in my backlog though, so I'll get to it eventually).