DataTables / DataTables/RowReorder

Handling Child Rows

Open
#4 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
23
Forks
27
PR merge metrics
No merged PRs in 30d

Description

I have been playing around using child rows in datatables along with the row reorder, but currently the child rows are not fully supported when reordering rows, so I have begun to work on a fix.
In order to better support the reordering of rows with attached children the following needs to happen:

  1. When creating the floating 'clone' row we should check for children, and if there are children rows we should include them inside the 'clone'.
  2. The border which is drawn around both the clone, and the original row when it is changing rows in the table needs to be extended to include any and all child rows.
  3. When the original row is moved upward in the table the child row needs to move with it(currently the child row only moves downward in the table with its parent.
  4. After the user moves a row the table is redrawn which automatically closes all of the child rows. If a table has a child row there needs to be an event listener for the 'redraw' event which will reopen any child row which was automatically closed.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing RowReorder's floating clone creation, border rendering, upward row movement, and redraw handling. Done means child rows are included in the clone and border, move with their parent in both directions, and reopen after redraw.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.