aleemstreak
aleemstreak
@MalikElate this is no longer the case, the InboxSDK now supports MV3
We have this scheduled for mid december. Happy to review and PRs earlier than that though if someone wants to take a stab at it.
I'm not sure making it a regular row that hides the vertical seperators is going to work because we wouldn't want clipping in the row. For example, imagine the title...
On the other hand, we'll prob need a way to figure out where the columns start and end in row because we might want to draw things in the group...
(and def agree on making this a first class feature because of the input handling)
Thanks for sketching that out. ### On scope: - might be better to first design this as a row grouping API where all the rows below a group row belong...
Sorry for the delay, we were discussing a bit internally. 1. How are you thinking about the isCollapsed property? Should the grid really handle that or should the app developer?...
1. Ah line numbers - that makes sense. Yes, we'll have to be careful that the grid never tries to request any data about rows in collapsed sections. 2. Great!...
Ohh the trailing rows, right. We'll need to do a trailing row for each row group.
I think we could implement trailing rows per group in user space actually