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
DateTime.MaxValue and DateTime.MinValue operate based on the local timezone/offset instead of UTC. This leads to incorrect date representations. For example, instead of getting 9999-12-31 for DateTime.MaxValue, it results in 10000-01-01 due to the timezone offset. This discrepancy causes errors when performing date range checks.
Repro code
openSystemletmaxMonth= DateTime.MaxValue.Month
printfn $"Max Month: {maxMonth}"// for timezone Sat Jan 01 10000 00:59:59 GMT+0100 (Central European Standard Time)// it gives 'Max Month: 1`
Description
DateTime.MaxValue
andDateTime.MinValue
operate based on the local timezone/offset instead of UTC. This leads to incorrect date representations. For example, instead of getting9999-12-31
forDateTime.MaxValue
, it results in10000-01-01
due to the timezone offset. This discrepancy causes errors when performing date range checks.Repro code
Related information
Fable version: 4.19.0
Operating system: macOS 14.5
The text was updated successfully, but these errors were encountered: