org.robolectric.util.Scheduler should use java.time APIs #8976
Comments
|
IMO Scheduler API should have been deprecated at the same time as LooperMode.LEGACY. I'll send out a PR to correct this. |
copybara-service bot
pushed a commit
that referenced
this issue
Apr 8, 2024
Scheduler API is obsolete and ShadowLooper APIs should be used instead. Related to #8976 PiperOrigin-RevId: 622908813
Closed
copybara-service bot
pushed a commit
that referenced
this issue
Apr 8, 2024
Scheduler API is obsolete and ShadowLooper APIs should be used instead. Related to #8976 PiperOrigin-RevId: 622943971
|
@kluever thanks for the post. These APIs are probably suboptimal. However, they are related to the legacy looper mode, which has been deprecated for 5+ years. There is not much point in investing a significant amount of resources to migrate something that is deprecated and obsolete to a more modern API. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Instead of using an ambiguous (w.r.t. the unit)
longto represent date/time concepts (like a delay or "now"), please use the appropriatejava.timetypes (DurationorInstant).There's a bunch of APIs in
org.robolectric.util.Schedulerthat could be improved usingjava.timetypes.The text was updated successfully, but these errors were encountered: