[time_picker]start date display is not inclusive
See original GitHub issueCurrently, we use Native filter on Superset version 1.2, but looks like The actual time range does not show correctly with SIP-15 (in the SIP-15 the time range must is [inclusive, exclusive) ). So that mean the actual time range and the tool tip must show label as: from_date <= col < to_date.
Expected results
Actual results
Environment
(please complete the following information):
- superset version:
1.2
- python version: `3.7
Checklist
- I have rated this issue on slack community and they advice me to create a ticket.
- I tried with the config SIP_15_DEFAULT_TIME_RANGE_ENDPOINTS = [“inclusive”, “inclusive”] but doesn’t help.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
JavaScript / jQuery date picker that allows both inclusive and ...
Inclusive date ranges start on the first day, and include the final day. These are useful for vacations for instance. · Exclusive date...
Read more >Datepicker startdate not working - Material Design for Bootstrap
startDay in Datepicker is not working const options = { format: 'dd-mm-yyyy', startDay: 1} const myDatepicker = new mdb.Datepicker(document.
Read more >Change how a date or time is displayed in a date picker, text ...
In the Display the time like this list, click (Do not display time). Click OK twice. Double-click the date picker, text box, or...
Read more >Should datepickers be inclusive or exclusive?
Do users expect datepickers to be inclusive or exclusive, and what are the exceptions? Does the same hold true when choosing just month...
Read more >Is input type="date" ready for use in accessible websites?
The lack of support in IE11, and more importantly in Safari on Mac. These browsers treat the date inputs as text boxes, which...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thanks for reporting, if you click view query from dashboard with a time filter, you will notice the query is actually accurate even though the display is wrong. we will push a fix for the display soon.
This bug was fixed in version 1.5.1 and should be marked as resolved.