Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Semi-persistent local filtering on table/view data through URL parameters #662

Open
datenangebot opened this issue Nov 10, 2023 · 2 comments · May be fixed by #1402
Open

Semi-persistent local filtering on table/view data through URL parameters #662

datenangebot opened this issue Nov 10, 2023 · 2 comments · May be fixed by #1402
Assignees
@enjeck
Labels
enhancement New feature or request medium effort medium Medium priority 🍂 2024-Autumn

Comments

@datenangebot
Copy link
Collaborator

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
@datenangebot datenangebot added enhancement New feature or request medium Medium priority medium effort labels Nov 10, 2023
@datenangebot datenangebot added this to the v0.7.0 milestone Nov 10, 2023
@datenangebot datenangebot mentioned this issue Nov 10, 2023
Open
@juliusknorr juliusknorr removed this from the v0.7.0 milestone Feb 15, 2024
@juliusknorr juliusknorr moved this to 🧭 Planning evaluation (don't pick) in 📝 Office team Apr 4, 2024
@juliusknorr juliusknorr changed the title Routeing for dynamical filters on views Semi-persistent local filtering on table/view data through URL parameters Apr 4, 2024
@juliusknorr
Copy link
Member

As a first step we should make sure that:

  • Local filters are applied and read from URL parameters
  • A user can copy the URL and when opening it the currently selected local filters are applied

In a second step we can think about storing them more permantently, but the above would already be a huge improvement.

A good example of how this can work is github projects, consider this example flow (parameter structure can be rethought):

  • Have a view open that has a server side filtered list of rows
  • A user searches for some text "test"
    • The local browser filter is adjusted in the URL (e.g. ?search=test)
  • A user filters a column title (column id 11) to contain "word"
    • The local browser filter is adjusted in the URL (e.g. ?search=test&filter[]=11:contains:word)
  • A user add sorting for the priority column (column id 12)
    • The local browser sorting is adjusted in the URL (e.g. ?search=test&filter[]=title:contains:word&sort=12:asc)

@juliusknorr
Copy link
Member

@enjeck I think this would be a nice task to take some time learning more about vue-router

Nothing urgent but you could line that one up to read up a bit on it already and look into on the side.

@juliusknorr juliusknorr moved this from 🧭 Planning evaluation (don't pick) to 📄 To do (~10 entries) in 📝 Office team May 8, 2024
@enjeck enjeck linked a pull request Oct 4, 2024 that will close this issue
Draft
4 tasks
@jancborchardt jancborchardt moved this to 🧭 Planning evaluation / ideas in 🖍 Design team Oct 17, 2024
@jancborchardt jancborchardt moved this from 🧭 Planning evaluation / ideas to 🏗️ At engineering in 🖍 Design team Oct 17, 2024
@juliusknorr juliusknorr moved this from 📄 To do (~10 entries) to 🧭 Planning evaluation (don't pick) in 📝 Office team Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@enjeck enjeck

Labels
enhancement New feature or request medium effort medium Medium priority 🍂 2024-Autumn
Projects
📝 Office team
Status: 🧭 Planning evaluation (don't pick)
🖍 Design team
Status: 🏗️ At engineering
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Semi-persistent local filtering on table through URL parameters nextcloud/tables
4 participants
@AndyScherzinger @juliusknorr @enjeck @datenangebot