-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Javadoc @inheritDoc tag is not handled in HTML output #159
Comments
I would also like to see support for the @inheritdoc annotation. I think I saw a post from @yole on another forum saying that
Wouldn't it be possible to both keep the default behavior of inheriting documentation if none is present and supporting the annotation? |
While mere |
I agree with @pdvrieze, I use {@inheritdoc} a lot exactly for that purpose. It allows to provide additional details, which is particularly interesting when you have different implementations of the same base type. |
I know I'm a bit late, but I'm interested by this too and since this issue has never been closed, I'd like to have it discussed again. |
Little late as well, but I too would also like this for the very same reason @pdvrieze said. |
Is this feature even being considered? It seems very helpful in extending base class/interface documentation as others have already pointed out. |
It should be fairly easy to do as a plugin when the |
When dokka processes a Java type using the
@inheritDoc
tag in its Javadoc, it is rendered as is in the Dokka HTML output.I would be expected that it is replaced by inherited documentation or at least link to it.
For an example, see the list of
Inherited Functions
hereThe text was updated successfully, but these errors were encountered: