-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support extended cron syntax #435
Comments
Thanks for the resource. I've gone back and forth on supporting extended characters before. Mostly my issue is that I just don't have time to build out the support myself. If you've done it I'd review a pr for sure. Thanks! |
Hi, |
@Deepak13245 did you ever end up making any progress on this task? |
Any update on this? Thanks in advance. |
I propose we implement the following extended characters list:
source: this only leaves out the |
I'd find this particular extended syntax incredibly useful for my project. Just wondering if there's been any progress here, or if there's anything I can do to help make it happen. Thanks! |
Hey there! Because we maintainers have had a very low bandwidth lately, we are waiting for volunteers to pick up on some of the waiting feature requests. If you'd be interested in taking a shot at implementing the extended cron syntax, I'd be glad to entertain any PR and give a hand if necessary! |
Picking this up |
Great! Don't hesitate to open a draft PR as soon as you have some changes if you'd like some guidance 😃 |
Yeah will do today. |
Does this package have any plan to support non-standard cron syntax?
Like, https://en.wikipedia.org/wiki/Cron#Non-standard_characters
I am using this package really well but I needed to use extended syntax for some reasons.
Now I extended the codes myself but it would be great if these syntaxes are supported natively.
Feature specification: #435 (comment)
The text was updated successfully, but these errors were encountered: