ngx-wapp-components 3.5.1 → 3.5.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +0 -17
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -19,23 +19,6 @@ After building your library with `ng build wapp-components`, go to the dist fold
|
|
|
19
19
|
|
|
20
20
|
Run `ng test wapp-components` to execute the unit tests via [Karma](https://karma-runner.github.io).
|
|
21
21
|
|
|
22
|
-
## Local table search persistence
|
|
23
|
-
|
|
24
|
-
Set a stable, unique `paginationId` on `w-table` or `w-tree-table` to persist
|
|
25
|
-
the page offset, page size, sorting and global search text in session storage.
|
|
26
|
-
The optional `StoreableTablePagination.query.searchInput` field stores the text.
|
|
27
|
-
|
|
28
|
-
- `w-table` restores search only when `wappTableObject.hasGlobalSearch` is enabled.
|
|
29
|
-
- `w-tree-table` restores the text of its global search input.
|
|
30
|
-
- Restoration updates both the visible input and the actual filter, preserving
|
|
31
|
-
the saved page within the filtered results, including when data arrives asynchronously.
|
|
32
|
-
- Clearing the search stores an empty string so an older search is not restored.
|
|
33
|
-
Calling `w-table.clearFilters()` also clears the visible and stored search.
|
|
34
|
-
- Existing entries without `searchInput` remain compatible and start with an empty search.
|
|
35
|
-
- Without `paginationId`, searching still works but its state is not persisted.
|
|
36
|
-
|
|
37
|
-
This search persistence does not apply to `w-table-lazy`.
|
|
38
|
-
|
|
39
22
|
## Further help
|
|
40
23
|
|
|
41
24
|
To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
|