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.

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

Executions filter still is applied even if user canceled it #5875

Open
smunteankestra opened this issue Nov 11, 2024 · 6 comments
Open

Executions filter still is applied even if user canceled it #5875

smunteankestra opened this issue Nov 11, 2024 · 6 comments
Assignees
Labels
area/frontend Needs frontend code changes bug Something isn't working

Comments

@smunteankestra
Copy link
Contributor

Describe the issue

Step 1 : Add a filter
Step 2 : remove it by pressing the X cross on it
Step 3: Refresh
Expected: filter to be removed
Actual: Filter remains

Screen.Recording.2024-11-11.at.10.31.44.mov

Environment

  • Kestra Version: develop
@smunteankestra smunteankestra added bug Something isn't working area/backend Needs backend code changes area/frontend Needs frontend code changes labels Nov 11, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Issues Nov 11, 2024
@MilosPaunovic MilosPaunovic removed the area/backend Needs backend code changes label Nov 11, 2024
@MilosPaunovic MilosPaunovic self-assigned this Nov 11, 2024
@sarthakvijayvargiya
Copy link

Hi @MilosPaunovic Can i work on this.

@MilosPaunovic
Copy link
Member

You can, but as this is a part of our new filters overhaul, I'll take over tomorrow if there's no PR submitted by then.

New filters are now shown only on Executions page (that is the name of the component, as well) so you can start there.

@MilosPaunovic
Copy link
Member

So, I've looked at this, and, as of this moment, it is expected behavior, as the search is being triggered only when we click the search button to the right.

We can update the expected outcome for the filters to be updated every time we remove a tag, like Stefan did here. Is that what we want from the product perspective @Ben8t?

@Ben8t
Copy link
Member

Ben8t commented Nov 12, 2024

Yes, I think the expected behavior from Stephan is the good one. Can we apply this to only "remove" action and not "add filter" (seeing the UI blinking every time a user add a filter doesn't sounds right in this case).

FYI, on GitHub Project filter, everything is applied at every change... (which make the UI blink a lot; not very UX friendly IMO, especially on adds)

@MilosPaunovic
Copy link
Member

Agreed, will make the necessary change.

@MilosPaunovic
Copy link
Member

Even better, @sarthakvijayvargiya, are you willing to have this as your first contribution, with a bit of help from my side?

You need to edit the kestra/ui/src/components/filter/Wrapper.vue component and add this router.push({query: encodeParams(current.value)}); to line 269, as part of the removeItem method.

Will wait for your PR if you're up for it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/frontend Needs frontend code changes bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

4 participants