Closed MrDarthShoe closed 3 years ago
Thank you for this report.
I've added the functionality on v0.1.3 and added it to the example, have a look and tell me if it works for you.
BTW, the UUID is added as a parameter into the run closure (1st param) if you want to get the UUID on the run callback.
Removing jobs on the fly works now. Thanks!
Removing job from
JobScheduler
seems to be unusable.remove
function takesUuid
of job which user want to remove:However, it seems that user cannot get Uuid of created job, because it is marked as private outside crate:
Possible solutions:
pub(crate)
fromJobLocked
definitionget_uuid
function