Not sure exactly what the feature request is here. A little bit more explanation might be necessary.
If you are looking to access your database in a table view you can always run yarn rw db studio this will start prima studio which allows you to edit and query your Prisma database in a table view.
Prisma Studio is designed for Admin Staff. I am looking at end user usage.
They would like to update few things.
May be update discount rate for a set of products. One would prefer to update it in spreadsheet form Vs change discount rate for one product at a time.
I’ve used ag-grid at my day job for situations like this and have found it to be pretty enjoyable to work with.
But, taking a step back, is this something that should be integrated into the framework, or something one would implement with the framework?
At first impression this use-case doesn’t feel broad enough to me to be shipped to every Redwood user, but I very well might be wrong. I’d be interested in hearing:
why I might not be thinking about this the right way
how - in general - the community thinks about what gets added to the roadmap and what doesn’t
Sidenote: from a UX perspective I love the interaction of users updating data in table directly without having to click an “update” button. I’ve always thought of this as one of those above-and-beyond interactions that can make an app feel really well designed.
If one looks at the sandbox examples of react-table, one can see a lot of standard boilerplate code. The promise of Redwoodjs is to do things easily by having the redwood scripts take care of all the boilerplate code.
I strongly recommend that redwood.js support editable grid cell as a standard offering