As originally described in #284,

Use case: I'd like to have "All Time" be a range, but want to avoid hardcoding some date like 1/1/1900.

ranges: {
    'Today': [moment(), moment()],
    'This Week': [moment().startOf('week'), moment()],
    'This Month': [moment().startOf('month'), moment().endOf('month')],
    'All Time': []
}

The callback just returns null for start/end dates if this is chosen.

I've updated example.html to demonstrate the new functionality.

showTime : true enables the time picker select lists minuteIncrement sets the minute dropdown increment (must be a number that 60 is divisible by) minHour and maxHour limits the hour dropdown to a range (will override 12hr clock if set)

Adding tt to the date format switches the time to use a 12 hour clock, showing an AM/PM select list accordingly :)

Hi,

I've added a new value for opens option - embed.

If you choose this option, then:

• the widget will be shown on init
• the hide function will be disabled
• the widget container will be appended after the HTML component it's attached to
• the CSS styles will remove float and position absolute, to make the widget resize normally

I know you did not plan to implement this, but maybe you could accept this PR? If you don't use it, it will not change anything.

I have added very basic localization support to date range picker. I don't know if you already had plans to do this another way. If that's the case, please let me know what you had in mind.

This would fix a state where notify() fires only if the range is present. If there is no range present ( same day selected ) or cancel has been clicked no notification would be send.

$('input[name="daterange"]').daterangepicker({ format: 'YYYY-MM-DD', startDate: '2013-01-01', endDate: '2013-12-31' }, function notify(start, end) { 
   console.log('A date range was chosen: ' + start.format('YYYY-MM-DD') + ' to ' + end.format('YYYY-MM-DD'));
});

This pull request expands the way you can select dates inside of the daterangepicker.

Changelist:

• There is now only one state for the date picker: You have one or more selected.
• You are no longer explicitly selecting beginning and end dates.

New date selection flows:

• Day A selected && Later Day B selected: Range A-B
• Day A selected && Earlier Day B selected: Range: B-A
• Day A && Day B selected && you select outside of range: range extended
• Day A && Day B selected && you select endpoint A or endpoint B: single day selected
• Day A && Day B selected && you select between A and B: single day selected

This flow seems very natural to me and doesn't stop anyone from using the daterangepicker the same way it was originally designed.

As the handling of left and right calendar was confusing our users, I tried to disable all the day's in the calendar's that are before the startDate, when it comes to the endDate selection. Hopefully this is fine?

When ranges{} object is defined picker not shown, because show-calendar class is removed, and when selecting a range picker are hide. This is not usual for people and for avoid this i add "showWithRanges" that are default false, but if setted to true avoid the hideCalendars() on clickRange()

allows you to completely reconfig the widget right before showing if needed. our form is two fields, and i needed to be able to change settings of each when activated. an example resetting the maxDate prior:

InputStart.on('before.daterangepicker',function(e,picker){ picker.maxDate = moment(InputEnd.val(),picker.locale.format); });

Sometimes it's necessary to set options without modifying the javascript. This pull request adds the flexibility to allow setting options through HTML5 data attributes.

This also eases the transition for people coming from bootstrap datetimepicker who already have existing code which uses data attributes: http://eonasdan.github.io/bootstrap-datetimepicker/#example5

This addresses issue #195

function (this.elements.outerHeight () incorrectly calculates the calendar position and returns [object Object]

http://bugs.jquery.com/ticket/12491 http://bugs.jquery.com/ticket/12159

Added the isInvalidTime function to allow validating times etc. This was useful for a particular use case where I want to disallow the selection of a time that is within a specific range of another.

Hey, I have been using Vitejs and Vue3. I was getting the following error while using your npm library.

"TypeError: moment is not a function"

It appears when inserted into the vitejs build, the library tries to use 'moment' however it receives an object instead of moment, the object contains a 'default' property that is the actual moment method.

I've added a check when the package is built via vitejs to check if moment is not a function and whether it has a default property, and if so, override moment with moment.default and continue as usual.

This change fixed the error on our project.

Thanks in advance for this awesome library.