You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is for design we are going to be expected to do various things with the data spreadsheets and right now I am not seeing a good way to implement some actionable cases in where it would be helpful if the data spreadsheets added support for this.
When updating a data set, if the column is removed the selection cell shouldn't crash the table. In my code I had to do this to avoid a crash since the selected cell didn't exist anymore.
if (document.getElementById("c4p--data-spreadsheet__cell--0--0")) {
document.getElementById("c4p--data-spreadsheet__cell--0--0").click();
}
I tried to use ref on the component but this won't work.
Marking this issue as high priority because there is a lot of features that would be very helpful to have right now but currently I have to manipulate in certain areas in order to get specific use cases to work or to fit the design.
Thanks!
The solution
Implement the suggestions above to make dev usability smoother with this component.
Hi @matthewgallo do you know when some of these can be started on and fixed? I opened another issue and added to this epic in relation to the selection area callback having some issues. Do you know what the process is for carbon team to begin taking a look at them? Thanks!
The problem
The issue is for design we are going to be expected to do various things with the data spreadsheets and right now I am not seeing a good way to implement some actionable cases in where it would be helpful if the data spreadsheets added support for this.
delete row
[Feature Request]: DataSpreadsheets: Add way to add custom actions to row index cell #5253setActiveCellCoordinates
,activeCellInsideSelectionArea
, and more.Allow
onDataUpdate
be functional in a way that we don't have to useuseState
and allow it to be likeonDataUpdate={(data) => computeNewData(data)}
I was able to figure this out. I needed to do something like this
I tried to use ref on the component but this won't work.
Marking this issue as high priority because there is a lot of features that would be very helpful to have right now but currently I have to manipulate in certain areas in order to get specific use cases to work or to fit the design.
Thanks!
The solution
Implement the suggestions above to make dev usability smoother with this component.
Design link
No response
Links to other materials
No response
Owner/main maintainer(s)
IBM
Second/backup maintainer(s)
No response
Product/offering
No response
Business priority
High Priority = pressing release
Code of Conduct
The text was updated successfully, but these errors were encountered: