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

[Bug] Named ValueTuple returns is not distinguished #9777

Closed
filzrev opened this issue Mar 9, 2024 · 1 comment
Closed

[Bug] Named ValueTuple returns is not distinguished #9777

filzrev opened this issue Mar 9, 2024 · 1 comment
Labels
dotnet Generate .NET API reference docs

Comments

@filzrev
Copy link
Contributor

filzrev commented Mar 9, 2024

Describe the bug

When generating API metadata for named ValueTuple with same type but different argument names.
Generated API document don't distinguish these ValueTuples.

To Reproduce

  1. Run docfx metadata command to following code
public class ValueTupleTests
{
    public static (int Ret1, int Ret2) Method1() => (0, 0);
    public static (int Ret3, int Ret4) Method2() => (0, 0);
    public static (int, int) Method3() => (0, 0);
}

2.1. When running on Debug mode with Visual Studio. Debug.Assert failed at following lines.

2.2. When running on Release mode.
Generated HTML display following Returns contents for ALL 3-methods

Returns
(int Ret1, int Ret2)

Expected behavior
Named ValueTuple returns contents are correctly displayed.

Context (please complete the following information):

  • OS: Windows
  • Docfx version: [e.g.2.75.3]
@filzrev filzrev added the bug label Mar 9, 2024
@yufeih yufeih added the dotnet Generate .NET API reference docs label Mar 19, 2024
@filzrev
Copy link
Contributor Author

filzrev commented Mar 19, 2024

Close this issue as dup of #9775 #8695

@filzrev filzrev closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet Generate .NET API reference docs
Projects
None yet
Development

No branches or pull requests

2 participants