Remove unclear FakeTimeProvider.Advance() overload
See original GitHub issueI am not a fan of the Advance()
overload method on FakeTimeProvider
that does not take a TimeSpan
and just increments time with 1ms. It is not obvious to the dev/user and is likely going to cause confusion to some.
I suggest removing it. If specific teams like the overload, they can easily add it back in via an extension method.
Issue Analytics
- State:
- Created 4 months ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Deleting conversions causing ambiguous overload?
The simplest solution would be to declare the operator bool as explicit . Used as a condition in a if , while or...
Read more >API to provide the current system time · Issue #36617
Our intention is to ship a ManualTimeProvider (or FakeTimeProvider or choose some other suitable name) that lets you set/change/advance/etc.
Read more >Announcing .NET 8 Preview 6
ExtractToDirectory overloads that allow users to provide a stream containing a zipped file and extract its contents into the filesystem. These ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t think it matters much at this point as if we end up supporting this publicly it will go through api review. Feel free to leave it out but I would have the extension method.
and maybe add an extension method Advance() just for this codebase.