How to omit constructor arguments on attribute?

[QFSW]

Operation System: Windows

DocFX Version Used: 2.51.0.0

Some attributes end up with very unwieldy constructors

Is it possible to still include the attribute decoration but remove all of its arguments from the api reference?

[KalleOlaviNiemitalo]

That output makes me wonder if there is a bug where Platform.AllPlatforms already includes all the other bits but DocFX lists them regardless.

[QFSW]

If this helps you understand the issue any better
In my code I have a bitwise flags enum Platform, so each bit represents one platform
Hence AllPlatforms is defined as ~0 to cover all platforms

[KalleOlaviNiemitalo]

I think the bug is here:

docfx/src/Microsoft.DocAsCode.Metadata.ManagedReference.Roslyn/Visitors/CSYamlModelGenerator.cs

Lines 896 to 909 in ac8024b

	if (isFlags)
	{
	var exprs = (from pair in pairs
	where HasFlag(namedType.EnumUnderlyingType, value, pair.ConstantValue)
	select SyntaxFactory.MemberAccessExpression(
	SyntaxKind.SimpleMemberAccessExpression,
	enumType,
	SyntaxFactory.IdentifierName(pair.Name))).ToList();
	if (exprs.Count > 0)
	{
	return exprs.Aggregate<ExpressionSyntax>((x, y) =>
	SyntaxFactory.BinaryExpression(SyntaxKind.BitwiseOrExpression, x, y));
	}
	}

DocFX uses the same algorithm for Visual Basic, as well:

docfx/src/Microsoft.DocAsCode.Metadata.ManagedReference.Roslyn/Visitors/VBYamlModelGenerator.cs

Lines 1315 to 1328 in ac8024b

	if (isFlags)
	{
	var exprs = (from pair in pairs
	where HasFlag(namedType.EnumUnderlyingType, value, pair.ConstantValue)
	select SyntaxFactory.MemberAccessExpression(
	SyntaxKind.SimpleMemberAccessExpression,
	enumType,
	SyntaxFactory.Token(SyntaxKind.DotToken),
	SyntaxFactory.IdentifierName(pair.Name))).ToList();
	if (exprs.Count > 0)
	{
	return exprs.Aggregate<ExpressionSyntax>(SyntaxFactory.OrExpression);
	}
	}

[KalleOlaviNiemitalo]

I mean, if Platform.AllPlatforms == (Platform)~0, and the argument of the attribute constructor is Platform.AllPlatforms, then DocFX should just emit that, rather than a huge bitwise OR expression. If that bug were fixed, then your HTML would get a much shorter syntax for the attribute, which could be good enough for you even though it would not satisfy your stated request.

DocFX could use the same algorithm as in Enum.ToString: convert the values of all enum constants to ulong, try them one by one from largest to smallest, subtract out the bits that matched, and finally list the corresponding names ordered by ascending value.