You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The year field is currently optional, with expressions being comprised of six or seven fields accordingly. I would like to also accept expressions which have neither seconds nor years, for a total of five fields. Importantly, expressions that do not include seconds but which do include years would be illegal.
The text was updated successfully, but these errors were encountered:
Importantly, expressions that do not include seconds but which do include years would be illegal.
To clarify this, the parser would treat any expression with 6 fields as having years. It would be impossible to detect the user's intent in some cases (e.g. * * * * * *), so this would simply be noted in the documentation.
May be use proxy object 'ScheduleBuilder'
I'm open to this approach. There are other settings that it would be nice to support -- e.g. whether day_of_week should be 0-indexed or 1-indexed, which varies between implementations. (This is relevant to #37.)
The
year
field is currently optional, with expressions being comprised of six or seven fields accordingly. I would like to also accept expressions which have neitherseconds
noryears
, for a total of five fields. Importantly, expressions that do not includeseconds
but which do includeyears
would be illegal.The text was updated successfully, but these errors were encountered: