Bug & Question: Handling of named jobs about croner HOT 8 CLOSED

1. Fixed in 6.0.1

from croner.

Unless you want to tackle this sooner, can probably make a PR before end of week

from croner.

Working on this right now 🏗️

from croner.

1. Nice finding, will fix asap!

2. There could be use cases where it's usable to leave the job in the array, so that the user can see that the job has existed but is stopped. However, it would be nice to have an additional method .destroy() which unlinks the job from the array, allowing it to be re-registered and garbage-collected. Will put this on the to-do-list if you're not up to it (?).

from croner.

There could be use cases where it's usable to leave the job in the array, so that the user can see that the job has existed but is stopped

I don't think there's a way right now to check is a Job has been stopped. To support that use case, would a new method like this makes sense?

isStopped() {
    return this._states.kill;
}

from croner.

Yep, that would make sense 👍

from croner.

Pre-released in 6.0.2-dev.0

from croner.

Released in 6.0.2

from croner.