Product

Hot Chocolate

Is your feature request related to a problem?

Since both the Hot Chocolate and ASP.NET Core AuthorizeAttribute are named the same, there's a high chance of the ASP.NET Core attribute being used on a Hot Chocolate resolver. This is problematic, since you think you've secured the resolver, but it isn't.

The solution you'd like

Throw an error during start-up if a Microsoft.AspNetCore.Authorization.AuthorizeAttribute is applied to a implementation-first resolver to alert the user of the misconfiguration.