Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: DataSpreadsheets needs more functionality support #5149

Open
2 tasks done
AustinGitHub opened this issue May 10, 2024 · 1 comment
Open
2 tasks done

Comments

@AustinGitHub
Copy link
Contributor

AustinGitHub commented May 10, 2024

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.

I was able to figure this out. I needed to do something like this

Component callback
  onDataUpdate={newData}


Function 
   const newData = (newData) => {
        const newRowData = newData(rowData);

        console.log(newRowData);
    }
  • 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.

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

@AustinGitHub
Copy link
Contributor Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs triage 🧐
Development

No branches or pull requests

2 participants