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
{{ message }}
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
Will add readme when have more spare time, thought that extension is fairly simple and self-descriptive.
why and how should we use it?
Extension gives warnings on places with potential side effects related to DateTime. Developed as a result of multiple discussions and big refactoring within the company I work.
DateTime.Now and similar can lead to some side effects in the code. Best practice is to have an abstraction somewhere on the top level. So in tests it would be possible to have a stub (or use RX Scheduler) and have predictable results.
Can you also add analyzer for replacing "DateTime" with "DateTimeOffset"?
I would, when I'll be able to make VS2017 work on my machine (was going to port it). But, in general, it's not really the goal. DateTimeOffset.[Utc]Now - still brings a static mutable state to the application, which leads to side effects.
Please add readme.
why and how should we use it?
Can you also add analyzer for replacing "DateTime" with "DateTimeOffset"?
The text was updated successfully, but these errors were encountered: