feat: configurable "My Contributions" tab in generic-list-view via ContentConfiguration

[SimonBurmer]

Add support for a configurable "My Contributions" tab in the generic-list-view that filters resources to only those where the current user has a relation (e.g. contributor, owner).

Motivation

The generic-list-view currently fetches all resources via the Kubernetes/GraphQL API and has no concept of per-user filtering. Teams want to give users a quick way to see only the resources they created or contribute to — the same UX pattern already present in the organization-ui workspace listing.

Technical requirements

This feature needs the search-operator, in order to filter for resources based on a defined relation.

Proposed ContentConfiguration API

Extend tabel-card with an optional tabs array:

{
  "ui": {
    "listView": {
      "tabs": [
        {
          "label": "All Components",
          "default": true
        },
        {
          "label": "My Contributions",
          "filterByCurrentUserRelation": "contributor"
        }
      ],
      "fields": [ ... ]
    }
  }
}

When filterByCurrentUserRelation is set, the tab switches the data source from the K8s/GraphQL API to the search API and applies a permissions filter for the current user + the given relation.

Example:

[gkrajniak]

Thanks @SimonBurmer on your input, the developmen in this library will focus on the extending the TableCard api to include the predefined filter functionality

export interface TableCardConfig {
// predifened table filters
   tableFiltersConfig: TableFiltersConfig
}

export interface TableFiltersConfig {
  filters: FieldFielterDefinition[];
  alwaysOnDisplay?: boolean; // default false
  // .... other identifed flags/metadata
}

export interface FieldFielterDefinition {

  label: string;
  /** Dot-separated path to the resource property (e.g. `metadata.name`). */
  property?: string | string[];
  /** Alternative path resolver with optional transforms. */
  propertyField?: PropertyField;
  /** JSONPath expression evaluated against the resource when `property` is not enough. */
  jsonPathExpression?: string;
  /** Static value — used when the cell shows a constant rather than a resource field. */
  value: string;
  /** Display and interaction configuration for this cell. */
  uiSettings?: UiSettings; // only buttons
}

The content configuration extension will be part of the platform mesh portal-ui-lib extension

btw. clean up the api the inerface should be in the declarative-ui\table and not the table-card realm or different place
export interface TableConfig {
export interface TableFieldDefinition

The filters buttons

• once selected shold change the dispay to activated,
• there can be only one filter active at a time, so switching from one activeted to other

[gkrajniak]

After discussion and feedback from the UX we decided to implement the tabs/filters in the following form:

figma.com/design/ZiIK4INJfUfwMyzo7FsC4y/Personalization?node-id=4099-52790