-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorder columns / edit column order as default view #607
Comments
Agree, we should bring the column ordering (without the checkboxes for hiding) and sorting to the "edit table" modal. Would suggest to reuse the order_weight property for each column as used before and add a sorting property on the db side. |
Hi, I encountered this use case today, I didn't know that I had to create a view to be able to do that. While this is being solved, I was thinking that having a hint somewhere saying it's possible to rearrange the column with a view for the time being could be helpful, maybe in columns drop-down menus. |
Hi, I also encounter this use case. Being forced to create a separate view to change columns order is a UX problem. What do you think about all this @juliushaertl ? |
We'll work on this eventually! @Jerome-Herbinet |
Any news about this very usefull feature ? |
I see this feature is highly requested. I'll bring it up during the next feature planning and see if we can work on it! |
Is your feature request related to a problem? Please describe.
Right now it is impossible to reorder columns or show metadata columns on a table without creating a separate view.
Describe the solution you'd like
Create a hidden view object for each table, which would be a default view for this table. Allow users to edit it by clicking Edit table in the menu. Renaming the default view would rename the table, making this solution a complete replacement for the current editing window, which allows renaming only.
Describe alternatives you've considered
Allow to save a view as a default view, itstead of replacing editing dialogue.
Additional context
No response
The text was updated successfully, but these errors were encountered: