Shane Krueger

Normally that prefix is only added when an unhandled exception occurs, which can be changed by setting the unhandled execution error delegate. See [Processing Errors](https://graphql-dotnet.github.io/docs/getting-started/errors#a-nameprocessingerrorsaprocessing-errors) in the documentation. However, in...

Note that the test above uses the default configuration of the serializer, error info provider, and so on. Written in "long form", the test looks like this: ```cs [Fact] public...

If you have `ExposeExceptionStackTrace` set to `true`, as shown below, however, you will see the message in the form you described. ```cs services.AddGraphQL(b => b .AddSchema() .AddSystemTextJson() .AddErrorInfoProvider(o => o.ExposeExceptionStackTrace...

Note that in version 7 there is now a `ExposeExceptionDetails` property which may be what you need. So if you were to use this in v7: ```cs .AddErrorInfoProvider(o => o.ExposeExceptionDetails...

> .NET Core 3.1 will go EOL mid December 2022 and .NET 5.0 is already EOL (https://dotnet.microsoft.com/en-us/download/dotnet) > > Those targets could be removed as well when NET 7 is...

I agree and was thinking along the same lines.

I would add `IMetadataBuilder` so that we don't have extension methods intended for _getting_ metadata mixed up in the builder class. Also methods that use `IMetadataBuilder` would be (more likely)...

Custom directives that validate input values are not for the faint of heart! But my first thought is that perhaps you are overriding the wrong method within your custom node...

You can view that same file for v5 here: https://github.com/graphql-dotnet/graphql-dotnet/blob/5.3.3/src/GraphQL/Validation/Rules.Custom/InputFieldsAndArgumentsOfCorrectLength.cs @sungam3r would need to answer additional questions here. I’ve not used directives, sorry.

Typically I do it within the field resolver. I would agree that a validation rule based on directives is a better approach, as the mutation or query can be validated...