Unfortunately we cannot use the current approach as it will have a performance impact if we call update settings ( it will rerender the table itself once again and we can have multiple tables with thousands rows and dynamic configs ), so we patched up temporarily and the plugin doesn’t give an error.
I just wanted to update you on this subject. The following issue has been fixed in v8.0.0. We will release v8.0.0 later today. I highly recommend updating.