You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed here: #4552 (comment) that when inputing a string for TimeOnly, HC is expecting a TimeSpan instead. Why is that? I would expect to be able to put in "14:00:00" as my time only but that's not the case. I noticed even the tests in that pull request use strings like that, not TimeSpans.
The solution you'd like
I would like it to have a parser for TimeOnly instead of it defaulting to TimeSpan. Maybe it was a typo? I'm going to create one for the project I'm working on. If it's good enough I'll maybe open a PR to see what y'all think.
The text was updated successfully, but these errors were encountered:
Because we do not really have a time scalar ... the scalar is called TimeSpan. We would not add a time scalar until there is a spec for it that goes well with the Date and DateTime spec.
Apologies for continuing the conversation after it's closed, but I think that TimeOnly should not be supported at all then. I would argue for reverting that PR from a while ago. Because a TimeSpan != TimeOnly
Product
Hot Chocolate
Is your feature request related to a problem?
I noticed here: #4552 (comment) that when inputing a string for TimeOnly, HC is expecting a TimeSpan instead. Why is that? I would expect to be able to put in "14:00:00" as my time only but that's not the case. I noticed even the tests in that pull request use strings like that, not TimeSpans.
The solution you'd like
I would like it to have a parser for TimeOnly instead of it defaulting to TimeSpan. Maybe it was a typo? I'm going to create one for the project I'm working on. If it's good enough I'll maybe open a PR to see what y'all think.
The text was updated successfully, but these errors were encountered: