Optional<T> has incorrect behavior when value for input argument does not exist in gql variables

[tatarenkoigor]

Is there an existing issue for this?

• I have searched the existing issues

Product

Hot Chocolate

Describe the bug

When using the Optional type for input arguments, get incorrect behavior when there are no variable values ​​for optional arguments in the gql query.

mutation UpdateCource($id: UUID!, $name: String){
  updateCourse(input: {id:$id, name:$name}){
    id
  }
}

//variables
{
  "id":"08db8c2a-3775-ab62-ee9c-00d956620000"
}

I receive in resolver value for this argument {hasValue: true, value: null}

I expect {hasValue: false, value: null(unspecified)}.

Steps to reproduce

1. Create input type

public class UpdateCource
{
    public Guid Id { get; set; }
    public Optional<string?> Name { get; set; }
}

2. Run mutation

mutation UpdateCource($id: UUID!, $name: String){
  updateCourse(input: {id:$id, name:$name}){
    id
  }
}

//variables
{
  "id":"08db8c2a-3775-ab62-ee9c-00d956620000"
}

3. Wrong result in Name argument

4. Expected result in Name argument

Relevant log output

No response

Additional Context?

No response

Version

13.4.0

[Boooober]

Really struggling with this stuff on our project.
Workaround is to write different queries for setting and clearing fields, but this seems like overkill on the frontend side.

[michaelstaib]

This is fixed with 13.6.0-rc.1