jens-scheffler-bosch commented on issue #34726: URL: https://github.com/apache/airflow/issues/34726#issuecomment-1745511216
I also once thought about this but myself then had use cases for testing where I needed these fields. So I agree that in most cases hiding these fields would make life easier for "normal" users - but still there need to be a way to influence the values for advanced cases. So far I did not spend much time and the adjustment of the Trigger UI was solely made in the content part of the form not taking the holistic perspective of usability into consideration. There might be also a few other things which might be optimized (on top of the things mentioned here). So I like the incremental approach :-D Two options as solutions to the raised issue (ad-hoc, other opinions and ideas welcome) are: * We "hide" the two fields in an accordion like the generated config section per default, users are not confused but you are able to unfold and configure * (One step further): We move these elements into the "Generated config" section and save a few pixels on top of the form but unfold with accordion when the generated config is presented I would not prefer having some kind of "global configuration" to control the form layout. Then in special cases where the fields are needed you need to adjust config and restart webserver. Also I would not like adding further DAG attributes or pseudo-params in the DAG config just to control the display. If other options match I could offer raising a PR as improvement, but before putting efforts I assume more opinions are needed. -- 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]
