influxdata / influxdata/influxdb
Don't refetch tags on time range modification
Open
team/ui
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Currently, each time we modify the query time range, we make another call to populate the list of measurements and tags. This is a weird UX.
We should pick a reasonable default time range (`1w`?). If the user picks a range that exceeds 1w, then we can make another call to update the list.
Contributor guide
Research direction
No file or test is named in the issue. Start at the query UI path that populates measurements and tags, reproduce a time-range change, and verify that ranges within 1w do not refetch while longer ranges do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- databases, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100