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
{{ message }}
This repository has been archived by the owner on Mar 7, 2019. It is now read-only.
Sorry for not responding sooner. This might be do-able, but I think it will be a decent chunk of work. I believe the difficult part will be actually determining which method is being overridden. At a minimum the type hierarchy would need to be modeled and some understanding of generics would need to be added (to handle overriding methods with generic parameters).
I'd be happy to review a PR (a design proposal might actually be a better place to start for this), but I unfortunately don't have the time to work on this myself in the near term.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the documentation of a subclass/interface is extended using a {@inheritdoc} tag, such a tag is not processed by javasphinx.
Instead of showing the documentation from the superclass/interface, the {@inheritdoc} tag just shows up in the built documentation.
An example of this issue can be found here.
The text was updated successfully, but these errors were encountered: