Cell merging
Closed this issue ยท 9 comments
Hi @lvyandev ! This improvement is in the planning.
Requires #42
Hi @lvyandev !
Do you expect to use cell sorting and merging in the same table?
There are some usability issues regarding sorting in these cases. It gets worse considering that it would be possible to make a cell occupy more than one column.
Since a cell can span more than one column and row, it gets a bit awkward to use the current API that builds the data based on rows. In this scenario, the data should be more column and row independent. They would just be independent cells. In that case, again, it wouldn't make sense to have ordering.
I'm telling this whole story because I'm thinking about forking this project into another one focused more on cell vision. I believe it would be better for a cell merge.
It doesn't matter, feel free to do the change.
Hi, @caduandrade is this feature available yet?
Guys, sorry for the delay. I know this feature is long awaited but also very complex because it conflicts with almost everything that already exists. I'm working on a significant performance improvement and at the same time already thinking about how to make cell merge viable.
Thank you for the information, @caduandrade. I wait for this feature. If this feature is implemented, this package would be great because most of all packages in pub don't have this feature.
Starting, better late than never... It will be impossible to avoid inconsistencies, the developer will need to pay attention to this. Ex.: ordering may generate collision. In this case I will try to create custom handlers but other inconsistencies should be the developer's concern.
I expected it to be complex but it was more than I expected ๐. One more for the next version 4.0.0.