jscheffl commented on issue #44256: URL: https://github.com/apache/airflow/issues/44256#issuecomment-2492357015
Answering the question here: I'd propose to DROP this legacy UI parameter. It is from ancient times - and the method of triggering is anyway different in the new UI. In the past we had the UI showing the JSON. Then AIP-50 was implemented which rendered the UI.,. or skipped. But in the new UI anyway the modal will be displayed. Why? Because I assume the user should confirm the trigger. Should not be a single-click to start a DAG "by accident". And the current modal also has the advanced options in the accordeon - no need to have a config option for this. The only question is if the information about the form parmaeters should be pre-fetched. I propose the follwing approach: When the user opens the modal a request is made to get the DAG params. While the resuest is running a spinner can be displayed above the accordeon. If params are defined then the spinner can be replaced with the form and the modal can grow in size. If no params the spinner could just be hidden. -- 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]
