The MUIDatatable documentation specifies that there is no tableCols prop. However, in the codebase, there are inconsistencies: some components pass both columns and tableCols with same arguments, while others use only columns.

To eliminate this ambiguity, it’s important to note that columns is designed to define the table headers and manage the visibility of specific columns. Standardizing the use of columns across the codebase would avoid confusion.

You are completely right @capricorn-32 but sistent component are the base component which is been used across all the projects of Layer5, making any major change in the prop type or removing any prop, will lead to a major break and leads to breaking change across all over the places it is been used.

Although all the components is been documented.

Just to avoid all this pain, I tried to make a change in a way a that, it should be fixed without changing the behaviour or the current component.

I can remove the tableCols props as there is no use of it, but it will lead us to major change in all over the code bases.

@mdkaifansari04 I am pointing this because in future it will more pain to work around this. Lets see, what decision should be made to prevent this.

One way to fix this would be change in component and update the docs,

After just the release we have to make changes in the corresponding projects as I've access to all the projects eventually.

I can make the changes but I'm busy in some school stuff might not be possible now.

If anyone shows up we can create issues for each repo.