Proposal: Better wildcard support in Cron about klasa HOT 7 CLOSED

I know I won't add support for @reboot or ?. They don't really work in our paradigm.

@annually will take 2 seconds to add. And using Math.random() H could be added very easily.

But L, W, and # are all going to take a significant amount of code and thought. I personally would like L and #, I am not sure about W though. These wildcards may not be added before the 1.0.0 release.

from klasa.

For ? we can use minute, hour, day, month, weekly methods from Date depending on the position of the wildcard. Should be easy to implement though.

Yes, we already discussed about @reboot not being to be implemented, that's why I didn't include it in the description.

from klasa.

? would only work on the moment the cron is generated; not consistent with the reboot time (each other). If that's ok, i could add that easily too... But this structure should be independent. So no client, or passing in the client start time.

from klasa.

You always have access to new Date() or Date.now() which return the current date or timestamp respectively. And we also do some wildcard changes, for example the pattern '0 0 * * mon,fri' gets stored as '0 0 * * 1,5' (as Sunday is 0), we can make this process and turn '? ? * * *' into '8 15 * * *' (it's 15:08 (UTC) right now), then, store the cron as that pattern instead of keeping the ?s.

from klasa.

We could also use the same approach taken in https://github.com/bunkat/later

parse('every friday at 5pm')
parse('every 5 minutes')

from klasa.

That's certainly more understandable, for people who don't know Cron. The current system uses Cron notation, however.

from klasa.

No plans to add this for the foreseeable future unless someone wants to take this up. Closing this issue for now.

from klasa.