bbovenzi opened a new pull request, #76953: URL: https://github.com/apache/airflow/pull/76953
The Dag list keeps its filters only in the URL, and both links back to it, the Dags button in the nav and the Dags tab next to Dag Runs and Task Instances, pointed at a bare `/dags`. Open a Dag or switch to Dag Runs, come back through either link, and the filters are gone. Back still worked, because that URL is in history. Both links now reopen the list with its last filters and search text. - The last query is held in memory in a small provider in `BaseLayout`, not in `localStorage`. Each browser tab keeps its own view, a new tab or a bare bookmark still opens the plain list, and a filter set last week doesn't come back unannounced. - Nothing writes the URL on landing. The link itself carries the query, so the first request already has the right filters and there's no effect to race `usePausedDefault` or a pinned preset. - Paging and sort (`offset`, `limit`, `cursor`, `sort`) are left off the link. Sort still falls back to the per-page default stored by `useTableURLState`. - Clearing every pill or pressing Reset empties the query, so the links go back to the plain list. Clicking Dags while already on the list now keeps the filters and only resets paging and sort. **Not covered here:** with `hide_paused_dags_by_default` on, a user who removed the Paused pill comes back with `paused=false` re-added, and a user with a pinned default preset who cleared every filter comes back to the preset. Both come from the landing defaults re-seeding a bare query. That belongs to the landing-state work around #76689, not to the links. This replaces the approach in #76238, which restored filters from `localStorage` with a landing effect. **Filters kept through the nav button and the Dags tab** <!-- drag files/pr-media/dags-nav-keeps-filters.gif here --> closes: #76235 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
