jsjasonseba opened a new issue, #48954:
URL: https://github.com/apache/airflow/issues/48954

   ### Apache Airflow version
   
   main (development)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Connection Extra Fields does not enforce required validation but shows 
required indicator
   
![Image](https://github.com/user-attachments/assets/0b7b6141-841e-47ed-ae70-658367c344a8)
   
   ### What you think should happen instead?
   
   Extra fields should not have required indicator. This is the case with 
Airflow 2.x
   
   
![Image](https://github.com/user-attachments/assets/a0a05dd6-653c-4ea3-9c96-5615c1d25c88)
   
   ### How to reproduce
   
   1. breeze start-airflow
   2. add connection with extra fields (e.g. google_cloud_platform)
   
   ### Operating System
   
   Ubuntu 24.04.1 LTS
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   Issue is caused by invalid isRequired logic in FieldRow component 
https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/ui/src/components/FlexibleForm/FieldRow.tsx#L33.
 
   
   The FlexibleForm FieldRow is a component shared by DAG Params field in 
Trigger DAG Form and also Extra Fields in Add Connection Form.
   
   The isRequired logic should have specific handling for Connection Form. To 
my understanding, Connection Extra Fields has never had a required validation. 
So, should we just set isRequired to always False in Connection Form?
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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