github-actions[bot] opened a new pull request, #74977: URL: https://github.com/apache/airflow/pull/74977
* UI: Add Select Recent Configurations dropdown to Trigger Dag form Reusing a past run's config currently requires leaving the trigger flow to hunt for the right run in the run list and use "Trigger again with this config". Restoring the Airflow 2 in-form dropdown lets users pick any distinct config from the recent runs in a scrollable list while composing a run. The dropdown reuses the existing dagRuns list endpoint and the same conf-only prefill path as the menu item, so no new API surface is added. closes: #69820 * UI: Regroup imports in RecentConfigSelect after rebase Main now separates React imports from third-party ones, and prettier flags the file otherwise. * UI: Keep user input when selecting a recent configuration Picking a recent configuration reused the re-trigger prefill path, which resets the whole form. A user who had already set a logical date, run id, note or manual data interval lost all of them. The dropdown is meant to swap only the run's conf, so it now leaves every other field untouched. * UI: Hide recent configurations when re-triggering with a run's config "Trigger again with this config" already fills the form with one specific run's conf, so showing an unselected recent-configurations dropdown on top of it is contradictory. * UI: Use system Select for the recent configurations dropdown The dropdown rendered inside the Trigger Dag modal was clipped at the modal edge because its content stayed inside the modal's DOM tree. The shared Select from src/system-components portals its content and already renders the control, indicator and positioner, so the hand-rolled Chakra parts only duplicated those layers. The trigger form tests also follow main, where the i18n mock returns keys and TriggerDAGForm no longer takes dagDisplayName. (cherry picked from commit 6fc06c600119c3948596ee1fd48c40cbb0325651) Co-authored-by: Wilson Josix Wang <[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]
