UI: Wire advanced-search toggle for Grid Triggering User filter - #70567
Merged
bbovenzi merged 1 commit intoJul 28, 2026
Conversation
The Grid endpoint accepts both the substring ``triggering_user`` and the index-friendly ``triggering_user_prefix`` variants, and the pill already exposes the substring/prefix toggle, but the Grid query hooks were only ever sending the substring param regardless of toggle state. Route the value through ``useAdvancedSearchArg`` so the toggle actually selects between the two variants on each request, matching the Run ID filter and the Dag Runs page.
dheerajturaga
requested review from
bbovenzi,
choo121600,
guan404ming,
pierrejeambrun,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
July 27, 2026 21:28
dheerajturaga
added
the
ready for maintainer review
bbovenzi
approved these changes
Jul 28, 2026
Contributor
|
Fixes issue introduced by #70150, moved 70150 to 3.4.0 so moving this one as well |
dabla
pushed a commit
to dabla/airflow
that referenced
this pull request
Aug 14, 2026
…he#70567) The Grid endpoint accepts both the substring ``triggering_user`` and the index-friendly ``triggering_user_prefix`` variants, and the pill already exposes the substring/prefix toggle, but the Grid query hooks were only ever sending the substring param regardless of toggle state. Route the value through ``useAdvancedSearchArg`` so the toggle actually selects between the two variants on each request, matching the Run ID filter and the Dag Runs page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Grid endpoint accepts both the substring
triggering_userand the index-friendlytriggering_user_prefixvariants of the Triggering User filter, and the pill on the Grid's filter bar already renders the substring/prefix advanced-search toggle. But the Grid query hooks were only ever sending the substring param regardless of toggle state — so the toggle effectively did nothing on the Grid.Route the value through
useAdvancedSearchArginuseGridRunsanduseGridStructureso the toggle actually selects between the two variants on each request, matching the Run ID filter wiring landed in #70150 and the Dag Runs page.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines