Open avedetvedea opened 1 year ago
Output cannot be copied with the caret, we have to copy all of it and then clip ourselves
We're going to be adjusting the UI to implement better copying experience. We'll ship a new 2.x EdgeDB with it improved in the next week or two.
Persist query option should be on by default
We'll start memorizing the preference in local storage in the next update. That should fix it for you.
because frankly it's pretty good.
@jaclarke James will take a look if we can make it work with INSERT/UPDATE too. But no guarantees here, the current implementation is pretty hacky.
If the page reloads for some reason the queries and outputs are lost.
This is a heavier change, we'll likely have to wait until 3.0 (where we actually redesign the UI to make it more logical and address your other points about persist query and long output). But James and I will discuss it next week, maybe we can backport some of the local storage fixes to 2.x.
more ideas: ( I will be updating my thoughts for improvements in this issue, because more and more people will be using the UI, with the new type-safe EdgeQL connections to clients, and practically every EdgeDB user when LSP lands 😋)
This is a heavier change, we'll likely have to wait until 3.0 (where we actually redesign the UI to make it more logical and address your other points about persist query and long output). But James and I will discuss it next week, maybe we can backport some of the local storage fixes to 2.x.
I just realized that we can traverse through the history with cmd+ {up, down} arrows. So the history is already saved in the local?, so persisting that after the page refresh shouldn't be subject to a redesign?
more ideas:
filter
in UI is freaky good. If it's easy, cmd+enter to run may be added there, tooData Explorer
Currently AFAI experienced we cannot stop queries after being run. When I close the tab in the browser it continues to run. A query of mine never returns, and takes up a single core of the CPU fully. I have to go to the activity monitor on MacOS to find its PID and kill it myself.
Some thoughts:
on
by defaultinput
should be collapsable, because if the query is long, to see the output we have to scroll down every single time (i.e., input and output should be collapse separately)