Skip to content

apps/panel 0.79.0 ​

English · Русский

Released on 8 September 2026. Previous release: 0.78.0.

What changed ​

  • Configured request.findAttributes filters are now passed to Table's API requests instead of being omitted.
  • Applied filters survive pagination, sorting, refresh, and reopening the table. Reset clears the filter dialog; Apply then removes the editable conditions. Cancel keeps the previously applied filters. Cleared filters do not revert to their configured initial values.
  • A table filtered through an attribute referencing the selected parent keeps that parent condition when the user clears editable filters. Changing the parent starts its first page and clears the previous child selection while preserving the user's filters. An older response cannot replace rows from a newer request.
  • If an object request fails, Table clears the previous rows and their selection and displays Retry. Retrying uses the current filters, sort order, and page. If a successful request returns an empty page but reports a positive total, page navigation remains visible so the user can go back.
  • Tables populated by a method no longer offer column sorting that the method does not perform. Filter comparison controls and row action menus have accessible names.

Configuration ​

Configure each condition in the table's request.findAttributes with field, compareType, and value:

json
{
  "type": "table",
  "request": {
    "findAttributes": [
      { "field": "isTemplate", "compareType": "EQUAL", "value": "true" }
    ]
  }
}

This fragment shows the filter setting only. Keep the table's existing id, data-source settings, and columns. isTemplate is an example attribute; replace it with the actual attribute name from the requested server meta type. Filter values are strings or null, including "true" in this example.

Updated documentation and demo ​

  • The Table guide explains initial and applied filters, parent selection, sorting, pagination, and recovery.
  • Its local demo instructions cover configured filters, parent and child rows, nested unit values, a simulated request error, and an empty later page. These examples use local demonstration data; they do not query the application's external API.