influxdata / influxdata/influxdb
Persist data explore queries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Proposal:
The ability to close the browser, change view in UI, or reload the page without losing the query I've been working on in the data explorer.
Current behavior:
The query dissapears when leaving the editor.
Desired behavior:
Would love to have the option to save the script editor query locally in my browser (local storage maybe), and be able to resume where I left off when an event occurs that causes the query to be lost in the current state of the UI.
Alternatives considered:
Not sure tbh
Use case:
This is important for me b/c I want to use the data explorer to explore my data and write non trivial flux queries. With the LSP dropping, I want to use it more than ever. The loss of my query has almost caused me a lot of grief. I've had to rewrite queries from scratch when my computer decides to go to sleep on its own 😳.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the data explorer's script editor and the UI state that currently loses the query when changing views, closing the browser, or reloading. Check how browser-local persistence could fit that flow; done means a non-trivial query can be resumed after each listed event without being lost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100