-
Notifications
You must be signed in to change notification settings - Fork 224
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
EDSC-4125: Recurring temporal slider doesn't work #1841
base: main
Are you sure you want to change the base?
Conversation
in draft, just running tests |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1841 +/- ##
===========================================
- Coverage 93.80% 82.41% -11.39%
===========================================
Files 778 778
Lines 18888 18991 +103
Branches 4849 4878 +29
===========================================
- Hits 17717 15652 -2065
- Misses 1123 3030 +1907
- Partials 48 309 +261 ☔ View full report in Codecov by Sentry. |
9c66a8f
to
cf5a966
Compare
static/src/js/components/Datepicker/__tests__/Datepicker.test.js
Outdated
Show resolved
Hide resolved
I'm seeing a behavior on this branch where on the temporal filter (the top level collection filter I mean) the recurring slider if enabled is only able to include the years so it cannot actually be moved vs on the granule filter we can still slide back to previous or post times |
cb9a164
to
74a3546
Compare
static/src/js/components/TemporalSelection/TemporalSelection.jsx
Outdated
Show resolved
Hide resolved
static/src/js/components/TemporalSelection/__tests__/TemporalSelection.test.js
Outdated
Show resolved
Hide resolved
@daniel-zamora What effort level do you think converting Datepicker.jsx & TemporalSelection.jsx to a functional component would be? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely seeing some nice improvement here. One thing I noticed though, if a user does not have any dates selected when checking "Recurring" they end up in the state where the start and end slider handles are overlapping and the range cannot be changed. It would be nice if instead, the entire range was selected.
ae0a520
to
4903f8a
Compare
4903f8a
to
ee89915
Compare
Overview
What is the feature?
On the granule temporal filter there are some issues that arise with the recurring toggle. If start and end have the same year, the InputRange handlers overlap and are unmoveable. When recurring is toggled on, you can still change year values with the date picker. And when you scrub the InputRange handlers left or right, on each step change it will send a search request to CMR
What is the Solution?
When the same year is selected for start and end via the datepicker, and recurring is toggled on, we max out the range from 1960 to w/e the end date is
When recurring is toggled on, the date picker will not allow you to traverse outside the bounds of a single year's worth of months(i.e. you cannot go to the previous month when on January or the next month after December) and the year is no longer displayed on the column header when in days mode. It prevents traversing by disabling the navigation buttons.
CMR searches are now only sent in the onChangeComplete callback, not onChange
What areas of the application does this impact?
Datepicker, TemporalSelection, and GranuleFilterForm components
Testing
Reproduction steps
Attachments
Please include relevant screenshots or files that would be helpful in reviewing and verifying this change.
Checklist