This is a use case that was discovered when integrating ClayTable with FDS where the selection column will always be visible and is not shown in the columns visibility menu. So we are adding a new API to allow omitting the column and always making it visible, something that is important for the table to continue functioning and is not necessarily part of the data structure. An option would also be to add the OOTB selection feature with controlled state, because this way, when clicking on select all, the dev can implement the selection of all items in the backend.
This is a use case that was discovered when integrating ClayTable with FDS where the selection column will always be visible and is not shown in the columns visibility menu. So we are adding a new API to allow omitting the column and always making it visible, something that is important for the table to continue functioning and is not necessarily part of the data structure. An option would also be to add the OOTB selection feature with controlled state, because this way, when clicking on select all, the dev can implement the selection of all items in the backend.