Beforehand the maxDate was only allowed to be the current date (+1970/01/01) or a date in the future (e.g. +1970/01/10). You couldn't set the maxDate to yesterday (e.g. -1970/01/02) or earlier in a logical manner.
All the functionality is in there, just needed the regex opened up to check for a plus or a minus at the start of the maxDate and minDate variables and parse them if present.
The licensing information is useful for different automated tools,
including WebJars.org. WebJars.org will not build and host a WebJar
for a project for which it cannot determine licensing. It first looks
for licensing information in bower.json, but will attempt to determine
the license by looking at certain files (e.g., "LICENSE").
Unfortunately, datetimepicker's license file doesn't have a "standard"
name. Also, I should mention that NPM is missing versions 2.4.1-2.4.3,
so an up-to-date version of datetimepicker cannot be built from NPM
using WebJars.org.
Added 2 new properties, to make a period of time disabled by setting disabledMinTime and disabledMaxTime.
I needed a way, to have minTime and maxTime set, but also a specific period of time within minTime and maxTime to be disabled. This can now be set with disabledMinTime and disabledMaxTime.
Example:
minTime: 12:00
maxTime: 22:00
disabledMinTime: 13:00
disabledMaxTime: 20:00
Then the available time will be 12:00 - 13:00 and 20:00 - 22:00
When options.weeks is true, and options.className is set, the result is
that both are concatenated together without a space to separate them.
For future maintainability, I decided to split out the modifications to
the datetimepicker element into separate modifications to more cleanly
show intent.
The today (home) button show the current month. After the double click it selected the current date and closed the popup, not validating the current date against the specified minimum and maximum dates.
Now, if the current date is out of the allowed range, the popup stays visible, and the input value is not changed.
