Support for 7 Segment Parsing?

[dbhc]

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 *)

[harrisiirak]

@dbhc what is your example use case? Year support isn't really part of default cron implementation, just mentioning.

[dbhc]

I have an engine that schedules jobs. (supports annual cron expressions) I'm currently using this library as a way to parse cron expressions to display the next expected run time on the front end. I currently have to sanitize the cron expression before parsing with cron-parser.

If the answer is no, there's no plans for annual parsing, that's alright too. I was just asking to plan accordingly. Thanks!

[beerran]

Any updates on this? We need this aswell. Using 7 segments is the default implementation of Quartz, which is a widely used tool for all types of scheduling.

[harrisiirak]

@beerran no updates at this point.

Using 7 segments is the default implementation of Quartz, which is a widely used tool for all types of scheduling.

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.

[lichangwei]

A fork that supports year segment: https://www.npmjs.com/package/@chuxingpay/cron-parser

[759325100]

@harrisiirak any update?

[harrisiirak]

@759325100 sorry, no updates :(

[emahuni]

Please this is a very useful use-case as this actually pins down a cron to run on a specific date.

[Ralireza]

up