Strawberry Shake: How can I override the automatic naming that occurs when two date fields appear in GraphQL query parameters?

[robc88Farm]

I logged this as a bug (#6971) but since it's not getting answered, figured that maybe it belongs in this section instead.

We have a query with a signature similar to this:
query TwoDates($first_date: date!, $second_date: Date!) { # etc. }

When I attempt to build, the generated Hasura client contains the following:

private readonly global::StrawberryShake.Serialization.IInputValueFormatter _dateFormatter;
private readonly global::StrawberryShake.Serialization.IInputValueFormatter _dateFormatter;

// in constructor:

_dateFormatter = serializerResolver.GetInputValueFormatter("date");
_dateFormatter = serializerResolver.GetInputValueFormatter("Date");


// and

private readonly global::StrawberryShake.Serialization.ILeafValueParser<global::System.String, global::System.String> _dateParser;
private readonly global::StrawberryShake.Serialization.ILeafValueParser<global::System.String, global::System.DateTime> _dateParser;


// in constructor:
 _dateParser = serializerResolver.GetLeafValueParser<global::System.String, global::System.String>("date") ?? throw new global::System.ArgumentException("No serializer for type `date` found.");
 _dateParser = serializerResolver.GetLeafValueParser<global::System.String, global::System.DateTime>("Date") ?? throw new global::System.ArgumentException("No serializer for type `Date` found.");

If I manually change the field names to get past the "two fields with same name" compiler exception, the build continues. This isn't ideal, obviously; is there a way to get around this--maybe a way to manually stipulate field names for query parameters?

Thank you.