Closed tanner0101 closed 5 years ago
Yeah, this is an annoying pain point right now. Adding another smaller unit seems like overkill since I'm not sure people will be scheduling things at that increment (although maybe they will?).
Yeah that's why I was thinking maybe schedule(at:)
for one-off jobs? That seems generally useful. Then in tests we could schedule a one-off job ~5 seconds in the future.
Yeah I think that’s the way to do it. That’s a helpful feature to have anyway
Right now the smallest unit of time scheduled jobs support is a minute. This makes waiting for the scheduled jobs test to run pretty annoying.
Maybe we should add seconds or a
schedule(at:Date)
method? This would allow us to run the tests a lot faster and could be useful to the end user.