You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
This case seems to be very similar to Case #415, but relates to dynamic parameters. For example StyleCop classic still finds this violation but not the analyzer. The violation of wrong type name XXX not picked up:
public class AuthorizationPolicy<TIDENT>
{
/// <summary>
/// Initializes a new instance of the <see cref="AuthorizationPolicy{XXX}"/> class.
/// </summary>
public AuthorizationPolicy()
{
Id = Guid.NewGuid().ToString();
}
The text was updated successfully, but these errors were encountered:
According to the C# compiler, there is no difference between AuthorizationPolicy{TIDENT}, AuthorizationPolicy{T}, and AuthorizationPolicy{XXX}. All of them reference the same generic type AuthorizationPolicy<TIDENT>.
I think this would make the most sense as a new rule, as opposed to updating existing rules to start checking this. FWIW I would be in favor of the rule. Even if it's not accepted for StyleCop Analyzers, I would accept it for DocumentationAnalyzers.
Hi,
This case seems to be very similar to Case #415, but relates to dynamic parameters. For example StyleCop classic still finds this violation but not the analyzer. The violation of wrong type name XXX not picked up:
The text was updated successfully, but these errors were encountered: