Inconsistent bug prone timezone argument order about croner HOT 2 CLOSED

A proposed fix is pushed, which make second and third argument completely interchangeable.

The reason I cannot use a fixed order is that both

const job = Cron('2023-01-23T00:00:00', { timezone: 'Asia/Kolkata' });

... and ...

const job = Cron('2023-01-23T00:00:00', () => { console.log('Yay') });

... is fully valid.

The first one is usable for checking next occurrance (using job.next() or job.enumerate(). While the second one is used for scheduling.

Previously, only the first of the next two example would work as expected.

const job = Cron('2023-01-23T00:00:00', { timezone: 'Asia/Kolkata' }, () => { console.log('Yay') });

But with the proposed fix, the following would be valid too.

const job = Cron('2023-01-23T00:00:00', () => { console.log('Yay') }, { timezone: 'Asia/Kolkata' });

I also added type checking of these two arguments.

The updated documentation can be seen on

http://hexagon.github.io/croner/Cron.html

from croner.

Now released in 4.3.3

from croner.