Semi-persistent local filtering on table/view data through URL parameters
@enjeck is already working on this.
Since May 8, 2024.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Is your feature request related to a problem? Please describe.
Don't create for all possible contexts different view. Thats also limited by thinking about sharing and dynamical adding needed views.
Describe the solution you'd like
Define a filter setup for views that can access filter data from the url and add it dynamically to the views filter.
Example:
Assume you have a list of assets maybe a software inventory. Now you want to know everything about one engine, so you would like to filter for that engine ID given by the url.
Filter setup for that view could look like:
Filters:
-> state = active // show only active assets
-> engineID begins-with urlValue(engine)
url could look like: domain.tld/index.php/apps/tables/api/1/views/rows?engine=ABCDEF
This would also add a selection option next to the search input in the web ui. It will offer all possible values for this filter, preselected with the url given value.
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.