Allow NCronTab to parse seconds as well

[vininu]

From https://github.com/atifaziz/NCrontab README.md

The default format parsed by CrontabSchedule.Parse is the five-part cron
format. In order to use the six-part format that includes seconds, pass a
CrontabSchedule.ParseOptions to Parse with IncludingSeconds set to
true. For example:

var s = CrontabSchedule.Parse("0,30 * * * * *",
                              new CrontabSchedule.ParseOptions
                              {
                                  IncludingSeconds = true
                              });

---

That would be very useful and is backward compatible.

[albert-kunushevci]

This cannot be possible using the current approach on TickerQ since we will have lot’s of issues, because of version of EFCore project which is using .net standard but we are creating a specific version for .Net8 and .Net9 which we will make lot’s of optimization using new ef core ability and will add support of second segment as well.

[vininu]

Which branch are you working with on that?

…

On Thu, Aug 28, 2025, 21:14 Albert Kunushevci ***@***.***> wrote: *arcenox* left a comment (Arcenox-co/TickerQ#220) <#220 (comment)> This cannot be possible using the current approach on TickerQ since we will have lot’s of issues, because of version of EFCore project which is using .net standard but we are creating a specific version for .Net8 and .Net9 which we will make lot’s of optimization using new ef core ability and will add support of second segment as well. — Reply to this email directly, view it on GitHub <#220 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTCSTAZ5V5QD3LKBSZJIID3P5BJLAVCNFSM6AAAAACFBJW2Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZUGQ4DCMZWHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[albert-kunushevci]

@vini-nu .net8 branch