Material-table: Warning: Unknown event handler property `onBulkEditRowChanged`. It will be ignored.

Created on 5 Aug 2020  路  12Comments  路  Source: mbrn/material-table

Demo

Describe the bug
When i try delete any row, the warning "Warning: Unknown event handler property onBulkEditRowChanged. It will be ignored" is showded:

To Reproduce
Steps to reproduce the behavior:

  1. Delete a row from table;

Screenshots
image

Desktop:

  • OS: Windows
  • Browser: chrome
  • Material-Table Version: 1.68.0

Aditional:
This doesn't hinder normal functioning, is only ocd :)

bug

Most helpful comment

Agreed, the reference in the sandbox is pretty clearly an internal library issue if it was looked at. We can see examples of the calls, such as in https://github.com/mbrn/material-table/blob/master/src/components/m-table-body.js

It really just feels like rather than reviewing the issue they closed it, blowing off those affected. I doubt that was the intent, but felt very dismissive

All 12 comments

same

Now, I can't add a new row, when i try, i get me this error:
image

To reproduce, just add a new row.

Also seeing this issue, for both adding a row and editing

Downgrade to v1.67.1 this work for me.

Downgrading also worked for me. Looks like an issue with the latest release. The same problem happens on their doc site as well.

+1

It was renamed to onBulkUpdate. So please use this moving formward.

Hi, I'm not sure why the issue has been closed
as you can see in the sandbox example, onBulkEditRowChanged isn't called

Agreed, the reference in the sandbox is pretty clearly an internal library issue if it was looked at. We can see examples of the calls, such as in https://github.com/mbrn/material-table/blob/master/src/components/m-table-body.js

It really just feels like rather than reviewing the issue they closed it, blowing off those affected. I doubt that was the intent, but felt very dismissive

Annotation 2020-08-29 181519
I think this error is by the this.props set.

Downgrade to v1.66.0 has worked for me.

Any resolutions for this? I am still seeing this on 1.68.0 and future releases too

Was this page helpful?
0 / 5 - 0 ratings