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 am writing to request support for the ISO 8601 standard 24:00:00 time format in .net. Currently, this format is not supported, and I believe that adding support for it would be beneficial for developers who need to represent midnight in their applications.
I understand that the current standard for representing midnight is 00:00:00, but the ISO 8601 standard allows for 24:00:00 as an alternative representation. This format is used in some industries, such as aviation, and it would be helpful to have support for it in .net.
The text was updated successfully, but these errors were encountered:
Tagging subscribers to this area: @dotnet/area-system-datetime
See info in area-owners.md if you want to be subscribed.
Issue Details
I am writing to request support for the ISO 8601 standard 24:00:00 time format in .net. Currently, this format is not supported, and I believe that adding support for it would be beneficial for developers who need to represent midnight in their applications.
I understand that the current standard for representing midnight is 00:00:00, but the ISO 8601 standard allows for 24:00:00 as an alternative representation. This format is used in some industries, such as aviation, and it would be helpful to have support for it in .net.
I am writing to request support for the ISO 8601 standard 24:00:00 time format in .net. Currently, this format is not supported, and I believe that adding support for it would be beneficial for developers who need to represent midnight in their applications.
I understand that the current standard for representing midnight is 00:00:00, but the ISO 8601 standard allows for 24:00:00 as an alternative representation. This format is used in some industries, such as aviation, and it would be helpful to have support for it in .net.
The text was updated successfully, but these errors were encountered: