prisma
Improve loading state for table + tree view
Should this be alleviated with triggering the requets for new rows sooner?
Here's few mockups for "placeholder rows" if we should need them though.
Will add in skeleton rows too, but with a few perf improvements in alpha.160, white spaces like the one you saw should become pretty rare!
IMO let's also defer this until after we have a way to know exactly how many records exist in a table. I can then show the correct number of skeleton rows. Thoughts?
IMO let's also defer this until after we have a way to know exactly how many records exist in a table. I can then show the correct number of skeleton rows. Thoughts?
I think there's no harm in filling the screen with skeleton rows even if there are less than displayed while loading. Agree @kuldar?
Will add in skeleton rows too, but with a few perf improvements in alpha.160, white spaces like the one you saw should become pretty rare!
Would be great to implement this soon as it's still very common for the cases I've tried. (I guess related to the fix for #106.)
@schickling @madebysid @kuldar is this being worked on? If not, any notion re: priority?
@idan It isn't, but since yesterday's discussion, I'm planning on picking this (and empty states) up soon. IMO pre-beta, since it isn't a whole lot of work anyway.
We'll do this for the table view.
We'll do it for the tree view if it takes less than 1 hour, otherwise we'll tackle that post-Beta.
Hey :wave:
Prisma ORM 7 introduces a brand new standalone Studio, built from the ground up to work everywhere, with or without Prisma ORM. Consequently, all "old Studio" issues are being closed as there won't be any further work on it. :mega:
The new Studio is also available in the Prisma VS Code extension and in the Prisma Console application. :electric_plug:
Help shape, improve and fix the new Studio with us in this repository by submitting bug reports and feature requests. :construction_worker:
