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 for 7 Segment Parsing? #174
Comments
@dbhc what is your example use case? Year support isn't really part of default cron implementation, just mentioning. |
I have an engine that schedules jobs. (supports annual cron expressions) If the answer is no, there's no plans for annual parsing, that's alright too. |
Any updates on this? We need this aswell. |
@beerran no updates at this point.
Yes, however cron-parser isn't currently fully compatible with Quartz implementation. Still, this feature as such is still worth to consider (and prioritize!) and it stays open as feature reguest, but I don't have any ETA for that - any PR for that functionality is welcome. |
A fork that supports year segment: https://www.npmjs.com/package/@chuxingpay/cron-parser |
@harrisiirak any update? |
@759325100 sorry, no updates :( |
Please this is a very useful use-case as this actually pins down a cron to run on a specific date. |
up |
Currently, adding the optional year segment to the cron expression breaks parsing.
Will support for this be added in the future? (ie
0 0 14 ? * MON *
)The text was updated successfully, but these errors were encountered: