Whitespace ... leniency

hi there,

crontab definitions are lenient with regard to the white space seperating the components of a schedule definition so that the following two lines are equivalent:

* 0    7,15       *    1-6
* 0 7,15 * 1-6

It is quite common for tabs to be used crontab files, unfortunately you module only accepts a single space as a delimiter between the components (mutiple spaces and/or tabs lead to parsing errors)

It would be nice if the parser could automatically normalize the input so that whitespace in a “schedule string” is treated the same way as is done by the various well-known cron applications found on posix systems. the normalization would need to be/do something like the following:

function normalize(input) 
{
   return (input + '').replace(/\s+/g, ' ').trim();
}

var testval = '0    7,15       *    1-6'
console.log(testval, normalize(testval));

Or maybe this is something you are opposed to?

[iamjochem]

btw - thanks for the quick response, it’s always nice when an author/maintainer replies especially when it’s within a matter of minutes.

I’ll get you a PR after dinner 😃

[harrisiirak]

@iamjochem yep there are some non-ISO timestamps in the tests. Going to clean up this in 3.0. Shouldn’t affect the normal usage of the library.