Skip to content
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

Incorrect display of generics in comment #896

Closed
joshuaavalon opened this issue Nov 15, 2016 · 3 comments
Closed

Incorrect display of generics in comment #896

joshuaavalon opened this issue Nov 15, 2016 · 3 comments
Labels
bug

Comments

@joshuaavalon
Copy link

@joshuaavalon joshuaavalon commented Nov 15, 2016

Minimal repro steps

<see cref="IEnumerable{T}" />

Expected result

What would you expect to happen if there wasn't a bug?

IEnumerable<T>

Actual result

What is actually happening?

IEnumerable<T><T>
@superyyrrzz
Copy link
Contributor

@superyyrrzz superyyrrzz commented Nov 16, 2016

Thanks you for your report. I can't reproduce this with your step, but this may be related to another bug introduced in DocFX 2.7. Do you meet the same problem if using DocFX 2.6.3?

@joshuaavalon
Copy link
Author

@joshuaavalon joshuaavalon commented Nov 17, 2016

Version 2.6.3 does not have this problem but 2.7.3 has this problem.

Here is my test file.

namespace Hello_World
{
    public class Program
    {
        public static void Main(string[] args)
        {
        }

        /// <summary>
        /// Test
        /// </summary>
        /// <param name="args"></param>
        /// <seealso cref="Test{T}"/>
        public void Hello()
        { 
        }

        public class Test<T>
        {
        }
    }
}

Here is the result of 2.7.3
sc

@superyyrrzz
Copy link
Contributor

@superyyrrzz superyyrrzz commented Nov 18, 2016

Thank you for your example. #900 will fix this. It will ship with DocFX 2.8 on 11/22.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.