Add Support for DateOnly type

[abhishekkumams]

Currently, GraphQL response is showing DateTimeFormat for date type columns.

If the value stored in the DB is 11-03-2017, graphql will show 11-03-2017T00:00:00Z.

[abhishekkumams]

@Aniruddh25, should we do this as well (Now, that we know how to do it and it will be easier to consume).
Maybe we can take this up in a future milestone?

[Aniruddh25]

@abhishekkumams, makes sense - I wonder why is that the case isn't Date type mapped to HotChocolate Date? https://chillicream.com/docs/hotchocolate/v13/defining-a-schema/scalars#net-scalars

[abhishekkumams]

@abhishekkumams, makes sense - I wonder why is that the case isn't Date type mapped to HotChocolate Date? https://chillicream.com/docs/hotchocolate/v13/defining-a-schema/scalars#net-scalars

Nope, It's mapped to DateTime

[Aniruddh25]

@abhishekkumams,

I went back into the previous changes and found this reasoning in the commit: 63d5ef2:

• DateTime
  This is a bit of a tricky one. DateTime type is handled by HotChocolate as DateTimeOffset. Also, our db column type detection method gives DateTime for all Date, DateTime, and DateTimeOffset. Meaning that while the user can define non DateTimeOffset columns, they will be interpreted as DateTimeOffset and the gaps will be filled with 00:00:00 time and local offset.
  HotChocolate also provides us with Date type. However, because all db column types Date, DateTime, and DateTimeOffset are detected as DateTime system types, we cannot make use of the HotChocolate Date type as of now.

So, to solve this, we would need to look for alternative ways for db column type to system type detection method other than ADO.NET Db Data provider.

[seantleonard]

@ayush3797 is this duplicate or secondary to your date work?