How might this have a positive effect on your organization?
It might make it a little easier to do testing of queries. I use a macOS clipboard history utility so I am a click away from my copy/pastes but not everyone does.
What is the current situation? Why does the current situation hurt?
Many admins are used to having up arrow key / down arrow key access to command history in a shell or Terminal.
What are you doing right now to work around this issue? What's non-ideal about it?
Copying & pasting.
Problem
The query field in Fleet accepts multiple numbered lines but has no command history. I think a reasonable cache might be the last 100 queries or something like that, it's potentially a pretty small amount of data, but I suppose browser state might be an issue for this capability to work seamlessly.
Potential solutions
Add a cache in the web app for command history data & a persistence cookie & maybe clear it out after 7d or 100 or the end of a session persistence token or however it works.
How might this have a positive effect on your organization?
It might make it a little easier to do testing of queries. I use a macOS clipboard history utility so I am a click away from my copy/pastes but not everyone does.
What is the current situation? Why does the current situation hurt?
Many admins are used to having up arrow key / down arrow key access to command history in a shell or Terminal.
What are you doing right now to work around this issue? What's non-ideal about it?
Copying & pasting.
Problem
The query field in Fleet accepts multiple numbered lines but has no command history. I think a reasonable cache might be the last 100 queries or something like that, it's potentially a pretty small amount of data, but I suppose browser state might be an issue for this capability to work seamlessly.
Potential solutions
Add a cache in the web app for command history data & a persistence cookie & maybe clear it out after 7d or 100 or the end of a session persistence token or however it works.
THANKS!!!!!