feat: Semi-persistent local filtering on table through URL parameters #1402
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #662
At the moment, you can try it out with the URL
http://local-nc-domain.com/index.php/apps/tables/#/tempview?tableId=1&columns=[1,2,3,4]&filter=1:contains:row&sort=1:asc
.It requires specifying the tableId, columns id and then the various filters and sort.
Still a lot a work to be done here:
View.php
is modified to store the columns and filtered/sorted rows that would be sent to the frontend. It will be better to create a separate file for this and avoid modifying the existingView.php
.?search=test
). Right now, I believe Tables searching is being done in the frontend using the search bar, not in the backend. So the easiest way to do this would be to just add whatever search term to the search bar.