table optimization (filtering, resizing and settings saved in user settings
This commit is contained in:
Executable
+21
@@ -0,0 +1,21 @@
|
||||
# AssetManager 0.5.5.69
|
||||
|
||||
## Changes
|
||||
|
||||
- Extended the shared table-filter logic with numeric and date comparisons.
|
||||
- Supported operators: `<`, `<=`, `>`, `>=` and `=`.
|
||||
- Inclusive ranges can be entered as `from x to y`, `between x and y` or `x..y`; German input such as `von x bis y` and `zwischen x und y` is supported as well.
|
||||
- Existing numeric range syntax in explicitly numeric software-summary columns, including `1-5` and `1..5`, remains available.
|
||||
- Date-only upper bounds such as `<=12.08.2026` include the complete selected day.
|
||||
- Applied the comparison syntax through the existing shared `data-table` filtering component, so normal client-side tables receive the feature without replacing their current text-filter behavior.
|
||||
- Extended the server-side recent-job filters with the same comparison behavior for job ID, priority and creation date.
|
||||
- Preserved existing filtering behavior.
|
||||
- Normal single-value substring searches remain unchanged outside the previously explicit numeric software-summary columns.
|
||||
- Line-based multi-value filters remain OR-linked within a column.
|
||||
- Filters across different columns remain AND-linked.
|
||||
- Existing sorting, persisted filter state and table resizing remain unchanged.
|
||||
- Updated German and English filter help text.
|
||||
|
||||
## Compatibility
|
||||
|
||||
No database migration is required. Existing table filters and server-side job filtering remain compatible with previously entered filter values.
|
||||
Reference in New Issue
Block a user