[Table] Add Visible Attribute to column Definition or NotVisible to Table component

[alwaqfi]

Hi,

At first, let me say thank you for this amazing and well build/rounded framework.

This is more of a request/discussion as it was mentioned in this Issue however it was closed for inactivity. I tried to see if there was a discussion started but couldn't find any (or my search words have betrayed me).

Use case:

In some cases we want to hide some columns based on certain criteria like permissions.
These columns we want to hide can be in different places in the table and we want to maintain this order. So, in this case it will be hard to re-add them to the array while maintaining the order.
With the current implementation columns property will contain all columns, and visible-columns will contain only visible columns.

Proposed solutions:

Solution 1: Add a new option to visible attribute to QTable Columns, and this property accept: Boolean | Undefiened (or just boolean and true is the default value)

columns: [ // array of Objects
  // column Object definition
  {
    // unique id
    // identifies column
    // (used by pagination.sortBy, "body-cell-[name]" slot, ...)
    name: 'desc',

    // if column is visible 
    visible?:  true // OR () => SomethingThatReturnsABoolean()

}

Solution 2: Add a new property to QTable called for example hidden-columns where it gets higher priority over visible-columns and will contain column names we want to hide.

QTable API:

hidden-columns: Array
Description
Array of Strings defining column names ('name' property of each column from 'columns' prop definitions); Columns marked as 'required' are not affected by this property

Work around solutions:

Possible solution 1:
By having columns as computed property where it returns only visible columns.
Possible solution 2:
By having visible-columns as computed field that is a clone of columns array and then remove columns we want to hide.

Solution 1 feels more natural than Solution 2 but both solution is not clean in my view as they require more logic to hide columns (remove or add them from/to the list).

I wonder if it is more logical to have one of the proposed solutions? I lean towards Proposed solution 1 since it can be done on the flight similar to format.

Thank you so much,
Asif