Say we have the following assay row (node names shown only:
sample1 named_process1 data_file1
And we insert a new row:
sample2 named_process1 data_file2
However: these four rows are only visible after we exit the sheet editor mode and re-render the tables. So basically, the user does not see the correct assay table while they remain in edit mode. Also, it will not be possible to edit two of those rows before exiting and re-entering edit mode. The "extra" rows should be rendered into the table immediately instead.
Requirements
Correctly add pooled/split rows into the assay table in the UI immediately after inserting the new row
Refer to the correct UUIDs for exiting nodes (of course)
The ordering of rows should be the same as it would after re-rendering the table
The last requirement might be tricky, I can't remember exactly how the ag-grid API handles this stuff. It might require re-rendering the whole table anyway, which also might be the easiest way to implement this..
I'll have to think about this in detail and come up with a spec. It's also TBD whether this should be done before or after #994.
Say we have the following assay row (node names shown only:
sample1 named_process1 data_file1And we insert a new row:sample2 named_process1 data_file2This will create the following rows:
However: these four rows are only visible after we exit the sheet editor mode and re-render the tables. So basically, the user does not see the correct assay table while they remain in edit mode. Also, it will not be possible to edit two of those rows before exiting and re-entering edit mode. The "extra" rows should be rendered into the table immediately instead.
Requirements
The last requirement might be tricky, I can't remember exactly how the ag-grid API handles this stuff. It might require re-rendering the whole table anyway, which also might be the easiest way to implement this..
I'll have to think about this in detail and come up with a spec. It's also TBD whether this should be done before or after #994.