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

\todo Commands in C# Not Showing On Generated ToDo Page (Origin: bugzilla #609709) #3673

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.6.1 on platform Other
Assigned to: Dimitri van Heesch

On 2010-02-12 02:12:39 +0000, Bradley Ward wrote:

Consider the code fragment below. Here is the errant behavior I am seeing:

  1. The @todo statements inside of the MyEnum enum class are being processed and appear in the documentation page generated for the for the MyNamespace namespace.

  2. But these same @todo statements are not included in the generated ToDo documentation page for this project.

Notes:

The MyNamespace namespace is documented via the use of a "@Package MyNamespace" command in a fake C# file named PackageDescription.cs in this same project.

namespace MyNamespace
{
public enum MyEnum
{
///
/// @todo Document this enum value.
///
VALUE_1,

    ///
    /// @todo Document this enum value.
    ///
    VALUE_2
}

///
/// @todo Figure out why the Doxygen todo items do not always 

appear in the docs.
///
public class MyClass
{
(snip)
}
}

On 2010-02-13 15:09:29 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2010-02-21 12:57:31 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment