You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Same problem as described in #4944
Describe the solution you'd like
sphinx checks if the base class is documented somewhere. If yes, it inserts the reference to the corresponding page automatically.
Describe alternatives you've considered
As originally proposed in #3104, allow autodoc-process-signature to return a list of strings that will be appended to Bases:
Additional context #4944 was marked as closed by #9233, but that PR unfortunately doesn't solve the problem: While I now can return a different base class, I still can't control the text of the hyperlink for that class.
With autodoc-process-signature being allowed to return strings, one could just return something like ':class:`telegram.TelegramObject`'
PS: maybe we can just reopen #4944 and continue discussion there …
The text was updated successfully, but these errors were encountered:
…nippet
This allows to inject a reST snippet through autodoc-process-bases
event. It helps to modify the base classes of any class to the expected
mark-up'ed text by custom extension.
Is your feature request related to a problem? Please describe.
Same problem as described in #4944
Describe the solution you'd like
sphinx checks if the base class is documented somewhere. If yes, it inserts the reference to the corresponding page automatically.
Describe alternatives you've considered
As originally proposed in #3104, allow
autodoc-process-signature
to return a list of strings that will be appended toBases:
Additional context
#4944 was marked as closed by #9233, but that PR unfortunately doesn't solve the problem: While I now can return a different base class, I still can't control the text of the hyperlink for that class.
With
autodoc-process-signature
being allowed to return strings, one could just return something like':class:`telegram.TelegramObject`'
PS: maybe we can just reopen #4944 and continue discussion there …
The text was updated successfully, but these errors were encountered: