github-actions[bot] opened a new pull request, #75994:
URL: https://github.com/apache/airflow/pull/75994

   * UI: Stop Recent Configurations flashing on the trigger form
   
   The section decided to hide itself only once its runs had arrived, so every
   time the trigger form opened it first drew an empty, disabled select and then
   either filled it or removed it. The query does not start until the modal
   opens, which reports as pending rather than loading, so neither flag on its
   own tells you the runs are in hand.
   
   Co-Authored-By: Claude <[email protected]>
   
   * UI: Lay out Recent Configurations like the rest of the trigger form
   
   Every other row in the form names itself in a column down the left and puts
   its control to the right. This one announced itself in small type above a
   control that ran the full width, so the eye had to change track in the middle
   of the form.
   
   Co-Authored-By: Claude <[email protected]>
   
   * UI: Offer recent configurations when they come from cache
   
   Runs stay fresh for five minutes, so reopening the trigger form inside that
   window serves them from cache without fetching. Asking the query whether it
   had fetched since mounting read that as "not ready" and hid configurations
   that were already in hand.
   
   Nothing needs asking. The options are built from the runs alone, so they are
   empty both before the runs arrive and when none of them carried a config, and
   in either case there is nothing to show.
   
   Co-Authored-By: Claude <[email protected]>
   
   ---------
   (cherry picked from commit 212fe09e1d0e384473b5ece2a2b1f66cff9e0a4b)
   
   Co-authored-by: Brent Bovenzi <[email protected]>
   Co-authored-by: Claude <[email protected]>


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