Aliased field in mutation input type does not get set when argument is a list

[chrisg2]

Description

Field values do not get set from an mutation's input argument when the field has an alias and the input argument is a list of input objects.

This appears to be in a similar vein to bugs #850 and #1358, but this behavior remains despite both those bugs being fixed. As far as I have observed, field aliases work if the mutation argument is a single value (not a list) - I have only observed this problem affecting arguments that are a list.

Steps to reproduce

See unit test at PR #1881.

Configure a field with an alias in MyEntityInputType:

public class MyEntityInputType : InputObjectGraphType<MyEntity>
{
	public MyEntityInputType() { Field("fieldAlias", x => x.BField); }
}

public class MyEntity
{
	public int BField { get; set; }
}

Configure a mutation like:

Field<BooleanGraphType>()
	.Name("mutateMyEntity")
	.Argument<ListGraphType<MyEntityInputType>>("multipleEntities")
	.Resolve(context => {
		var es = context.GetArgument<List<MyEntity>>("multipleEntities");
		es[0].BField.ShouldBe(4);
		return true;
	});

Execute a mutation query like the following:

mutation {
	mutateMyEntity( multipleEntities: [{ fieldAlias: 4 }] )
}

Expected result

The es[0].BField.ShouldBe(4) assertion succeeds.

Actual result

The BField value that comes through is 0 and the ...ShouldBe(4) assertion fails.

Environment

graphql-dotnet version 3.0.0

[Shane32]

@chrisg2 Thanks for the test; it demonstrates the bug very well.

@sungam3r Do you want to look at this or should I?

[sungam3r]

I will.

[sungam3r]

Done

[chrisg2]

Thanks for fixing!

[sungam3r]

https://www.nuget.org/packages/GraphQL/3.1.0