Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Explore] Timepicker time range interval design #12283

Closed
graceguo-supercat opened this issue Jan 5, 2021 · 9 comments · Fixed by #12308
Closed

[Explore] Timepicker time range interval design #12283

graceguo-supercat opened this issue Jan 5, 2021 · 9 comments · Fixed by #12308
Assignees
Labels
enhancement:committed Enhancement planned / committed by a contributor explore:time Related to the time filters in Explore P1 Priority item - Major

Comments

@graceguo-supercat
Copy link

graceguo-supercat commented Jan 5, 2021

How to reproduce the bug

  1. Go to explore view, click Date picker, choose Previous range type
  2. Current month is Jan, previous month should include 12/31

Actual results

Screen Shot 2021-01-05 at 9 44 54 AM

Environment

latest master

cc @junlincc @zuzana-vej @zhaoyongjie

@graceguo-supercat graceguo-supercat added P1 Priority item - Major explore:time Related to the time filters in Explore labels Jan 5, 2021
@junlincc junlincc added the #bug:cant-reproduce Bugs that cannot be reproduced label Jan 5, 2021
@graceguo-supercat
Copy link
Author

2020-12-01 <= col < 2020-12-31 means include 12-01, not include 12-31.

@junlincc junlincc removed the #bug:cant-reproduce Bugs that cannot be reproduced label Jan 5, 2021
@junlincc
Copy link
Member

junlincc commented Jan 5, 2021

looks like this is happening in all time setting(custom, last and previous), and the default state

Screen.Recording.2021-01-05.at.10.13.42.AM.mov

Screen Shot 2021-01-05 at 10 11 42 AM

@junlincc junlincc changed the title [date picker] Previous: end date is wrong [Explore] Timepicker time range END time operator should be "≤" Jan 5, 2021
@graceguo-supercat
Copy link
Author

If i want to see data of Previous month, it should includes data in 12/31. please check with @zhaoyongjie.

@graceguo-supercat
Copy link
Author

graceguo-supercat commented Jan 5, 2021

for display, Previous month should display as 2020-12-01 <= col < 2021-01-01, and it should include 12/31 data.

@junlincc
Copy link
Member

junlincc commented Jan 5, 2021

what about changing the END operator to "≤"?

@junlincc
Copy link
Member

junlincc commented Jan 5, 2021

acknowledging the severity of this bug as it is misleading users reading the chart. my bad not catching it before we merged. Thanks for reporting! 🙏

@graceguo-supercat
Copy link
Author

i feel we should display 2020-12-01 <= col < 2021-01-01 not 2020-12-01 <= col <= 2021-12-31.
This will be consistent with all other time range display format, which means include begin, exclude end.

@graceguo-supercat graceguo-supercat changed the title [Explore] Timepicker time range END time operator should be "≤" [Explore] Timepicker time range END time Jan 5, 2021
@junlincc
Copy link
Member

junlincc commented Jan 5, 2021

im suggesting to make this change universal and i believe using "<" is a bug not by design

looking at the old time picker, it had a similar problem on pill display. but actually including both start and end dates in the query.

Screen Shot 2021-01-05 at 12 00 37 PM

@junlincc junlincc changed the title [Explore] Timepicker time range END time [Explore] Timepicker time range interval design Jan 5, 2021
@junlincc junlincc added the enhancement:committed Enhancement planned / committed by a contributor label Jan 5, 2021
@john-bodley
Copy link
Member

@junlincc see SIP-15 as to why the start and end time range intervals are inclusive of and exclusive of respectively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement:committed Enhancement planned / committed by a contributor explore:time Related to the time filters in Explore P1 Priority item - Major
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants