-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
c#: Inherit documentation from interface property (not working as no docs displayed) #8898
Comments
Looks like a C# problem.
|
Thanks for the quick response. Here are the differences (but I noticed, not all were listed by using your command. Some labels in the gui are red, but not listed, I'll append them though.) Difference with default Doxyfile 1.9.2 (caa4e3d)PROJECT_NAME = xxx red colored labels are: The html filename is like: Does that help? Thanks |
Okay thanks. So here is the output from doxywizard:
|
…(not working as no docs displayed) See to it that the documentation of a C# property is copied as well.
I've just pushed a proposed patch, pull request #8904 |
issue #8898 c#: Inherit documentation from interface property (not working as no docs displayed)
Code has been integrated in master on GitHub (please don't close the issue as this will be done at the moment of an official release). |
Describe the bug
In the same assembly, I have a public interface containing properties and methods. Everything is documented. The implementing public class has the same properties and methods (of course) and intelliSense shows the docs from the interface of methods and properties. The generated docs (of the implementing class) only contain the docs of the methods, but not of the properties. These docs are completely empty. It also doesn't matter, if I use
<inheritdoc />
or not.Expected behavior
The documentation text from the properties of the interface should also be copied to the implementing class properties.
To Reproduce
Version
Windows 10, 64 bit,
doxygen 1.9.2
Thanks in advance for helping me. Let me know, if I can do anything to solve this problem.
The text was updated successfully, but these errors were encountered: