jscheffl commented on PR #60410: URL: https://github.com/apache/airflow/pull/60410#issuecomment-3910501449
> > Besides the potential glitch ^^^ - cool! Looking forward for follow-ups! > > One thing that came into my mind: Do you have an idea for a version merker that once we drop support in providers for Airflow <3.2 that we can clean the legacy field definition any leave only YAML behind? Something like `# TODO AIRFLOW_V_3_2_PLUS - we need to clean here` ? > > #protm > > Thanks @jscheffl you mean clean up the `get_ui_field_behaviour` and the other function for providers? Maybe we should add that in the hook code files? I wanted to say: - We should put a marker in the code at existing `get_ui_field_behaviour()` and `get_connection_form_widgets()` that we do not forget once we drop support < Airflow 3.2. But of course not before. - Also came into my mind and found airflow-core/docs/howto/connection.rst which describes the fields - so this description should be marked as deprecated and YAML structure be defined here. -- 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]
