Extension docstring magic

[jayvdb]

When the user has overridden a view, they are very likely to change the serializer, and not copy the docstring.

It would be nice if the extension system here used the main view docstring, unless the replacement provided its own docstring.

[tfranzel]

actually i was under the impression that this was already being done. inspect.getdoc will follow the MRO until it finds a docstring. at least that is what i understood from a quick glance over the implementation.

can you give an example where this is not the case?

[jayvdb]

Is it being done on Fixed and/or Fixed.post ? It needs to be both.

[tfranzel]

that was the cruial piece of information. i'll have a look at the methods again. for the classes it should already work as expected

[tfranzel]

inspect.getdoc was used improperly. on fixing it, it gave too much though. i still need to stop the discovery on the DRF base classes, because it would otherwise emit the generic DRF documentation if there is do docstring on one's own classes. almost there

[jayvdb]

Something like https://github.com/jayvdb/django-dunder/blob/1c589e3/django_dunder/_register.py#L36 ?

[tfranzel]

@jayvdb that is not enough to do it properly. check out this. i think that should solve your problem. please close if issue is resolved.

[tfranzel]

reopen if it does not work as expected

[jayvdb]

I cant re-open; I dont have permission to do that.