Ability to drag a row in to a new position

[andrewtpham]

Is your feature request related to a problem? Please describe.

Functionality

• We would like the ability for the h-table editable component to be able to have a draggable row feature where a user can click on a row and drag it into a position of their choice.
• We would like the ability for a row to be nested and put inside another item. For example, one or more project records could be put inside a portfolio. See Dots BE endpoints for portfolio: https://github.com/hikaya-io/dots-backend/issues/1118

This could be used in dots-fe on the table list page (not the import table page) or the metrics project and configuration pages as well as the new metrics table: #286

Additional context
Here are some references in a draggable row that I found:

• https://bestofvue.com/repo/mizuka-wu-el-table-draggable-vuejs-table
• https://github.com/SortableJS/Vue.Draggable
• Example of nested draggable component: https://sortablejs.github.io/Sortable/#nested
• There's a tree component in element with a draggable feature: https://element.eleme.io/#/en-US/component/tree#draggable

In this gif below, a project record could be an item that is nested:

• A portfolio is a group of projects
• A portfolio can be nested inside another portfolio
• A project can be on its own or inside a portfolio

Screenshots from the above GIF:

[TAnas0]

On nested Portfolios in the BE

Here is 2 things to do to make it possible:

• Add a nullable relationship from a Portfolio to itself to indicate if a Portfolio does have a "parent" Portfolio, or not
• Add an endpoint where we can move a Project from a Portfolio to another in a single call

And an additional question:

• Portfolios that have "children" portfolios, can they have Projects (as direct descendants)? Is this much like a directory structure, with Portfolios being directories and Projects being files?
  The Answer to the above question would require some additional considerations and implementations.

[andrewtpham]

@TAnas0 thanks for comment.

On your question:

Portfolios that have "children" portfolios, can they have Projects (as direct descendants)? Is this much like a directory structure, with Portfolios being directories and Projects being files?
The Answer to the above question would require some additional considerations and implementations.

I think the main purpose of children portfolios is to have another subset of projects for organization purposes making it easy to see how they can be grouped. But I could see the appeal of having the directory structure in place to maintain a clean logic. But I think it's more important to have the ability to organize and add projects to multiple portfolios