Skip to content

Conversation

@leandrocollares
Copy link
Contributor

Summary

This PR uses 2000 - current year as the default date range filter and implements record space exploration via date brushing.

Related issue: #332

leandrocollares and others added 30 commits October 29, 2025 10:42
@candicecz
Copy link
Collaborator

General comments:

  1. Duplicate queries:
    Currently all queries (both for filters and results) run once before the date filter is applied and then run again with the default filter (2000 to 2025). The date brush data needs to run without a date filter to display accurately but, the other queries should run only once, using the default date filter. This will avoid unnecessary repeated calls.

  2. Empty date-range behavior:
    Selecting a date range with no data causes both the slider and histogram to disappear (see image). Consider handling this empty state more gracefully. For example, keep the slider visible and show a clear “no data available” state for the histogram instead of removing the UI entirely. Feel free to apply a different solution.

image

@candicecz
Copy link
Collaborator

Future improvements:

  • Fix date inputs. They're currently exhibiting buggy behavior. Feel free to delete and rebuild components from scratch, if quicker.
  • Ensure URL-entered dates propagate correctly. If a user enters a date directly in the route, the histogram, slider, and input fields should all update accordingly. (Example route)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants