dheerajturaga opened a new pull request, #70150:
URL: https://github.com/apache/airflow/pull/70150

   The Dag Runs list page lets users narrow runs by Run ID, but the Grid view's 
filter bar offered no equivalent — forcing users to eyeball run columns to 
locate a specific run. This adds the same Run ID search to the Grid view so 
both surfaces filter consistently.
   
   ### Changes
   
   - **Backend** (`routes/ui/grid.py`): add `run_id_pattern` (case-insensitive 
substring, `ILIKE '%…%'`) and `run_id_prefix_pattern` (index-friendly prefix) 
query params to both grid endpoints (`get_grid_runs` and `get_dag_structure`), 
wired into each `filters=[…]` list — mirroring the existing pattern in 
`routes/public/dag_run.py`. No DB migration needed.
   - **Frontend**: add the existing `RUN_ID_PATTERN` filter to the Grid filter 
bar (`GridFilters.tsx`) and thread the value through the query chain 
(`DetailsLayout.tsx` → `Grid.tsx` / `Gantt.tsx` → `useGridRuns.ts` / 
`useGridStructure.ts`), parallel to the existing `triggeringUser` filter.
   - **Generated**: regenerated the OpenAPI spec and TypeScript client.
   - **Tests**: added `test_filter_by_run_id_pattern` and 
`test_filter_by_run_id_prefix_pattern` covering substring (incl. 
case-insensitivity), prefix, no-match, and both `runs`/`structure` endpoints.
   
   ### Testing
   
   - Backend: grid endpoint tests pass.
   - `mypy-airflow-core`, `ruff`, `tsc`, `eslint`, `prettier`, and the 
OpenAPI-spec / UI-compile sync prek hooks all pass.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.8)
   
   Generated-by: Claude Code (Opus 4.8) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
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]

Reply via email to