Guillaume Rochat

Hi @talon-vonneudeck, do you have a source backing that? It does like a very interesting option considering what you mentioned. I'll try to add it over the weekend.

Hi @gaboesquivel. In the first draft, we included ECS but as the search progressed, we thought it might be more appropriate to compare against CaaS rather than container orchestrators. Maybe...

@rmolinag Oh good point, we didn't see it that way initially. I'll try to add it over the week-end.

From memory, I assumed that seconds could be missing from the expression and we'd still have a valid expression, even with `seconds: true`. I could change that behavior, but that...

According the cron syntax spec, there is no limit to the steps values (aside from the divide by 0 you filed earlier), which I assume was to make it easier...

@XueMeijing That is not with this cron-validator package but with cron-validate. : https://github.com/Airfooox/cron-validate Example: https://runkit.com/embed/bxfrpxgls3o0

@rondsjinhuajin sorry for the late reply, I never received any notification. I would use the following library which supports more feature : https://github.com/Airfooox/cron-validate The preset `aws-cloud-watch` supports those, but not...

Ah, even better, you can override their config if needed: ```js cronValidate('0 0 12 L * ?', { preset: 'aws-cloud-watch', override: { useSeconds: true, useYears: false, } }).isValid(); ```