Overview of the problem

Oruga version: [0.8.X]

Description

In the current implementation of the table component, each element of the table data property (which is a user-defined array) is extended by a special identifier to implement specific behaviour of the table.

But this is a bad concept. It also results in unexpected behaviour for some users.

We shouldn't be touching the data props to set or recreate data.
We can resolve it without using an Object.assign to avoid cloning each row.
We can use an object map where the key is the row and the value is uuid.
Or table data is an array of our class/interfaces,

interface TableData { 
  key: any;
  data: any[];
}

In the future

TableData<T> {
  id: any;
  data: T[];
}