Skip to content

[v3-4-test] Keep Dag list filters when returning through the Dags link (#76953) - #77187

Open
choo121600 wants to merge 1 commit into
apache:v3-4-testfrom
choo121600:backport-76953-v3-4-test
Open

choo121600 wants to merge 1 commit into
apache:v3-4-testfrom
choo121600:backport-76953-v3-4-test

Conversation

@choo121600

Copy link
Copy Markdown
Member

Manual backport of #76953 to v3-4-test. The automatic backport failed on a conflict in BaseLayout.tsx.

v3-4-test has neither the navigation ProgressBar nor GridSelectionProvider in BaseLayout, so the conflict was resolved by keeping the branch's existing layout and only wrapping it in DagsListSearchProvider. The other files applied cleanly.

(cherry picked from commit 3d8302a)


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Opus 5.5

Generated-by: Claude Opus 5.5 following the guidelines

… link (apache#76953)

The Dag list keeps its filters only in the URL, and the Dags button in
the nav and the Dags tab above the list both pointed at a bare /dags.
Opening a Dag, or switching to Dag Runs, and coming back through either
link reset the list to its default view, so users had to rebuild the
filters each time. Browser Back worked; the links didn't.

The list's last query is held in memory above the routes rather than in
localStorage, so each browser tab keeps its own view, a new tab still
opens the plain list, and nothing writes the URL on landing to race the
paused default or a pinned preset. Paging and sort are left behind: they
describe where you were in the list, and sort already falls back to its
stored per-page default.

(cherry picked from commit 3d8302a)
@boring-cyborg boring-cyborg Bot added the area:UI Related to UI/UX. For Frontend Developers. label Nov 17, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:UI Related to UI/UX. For Frontend Developers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants