andrewD46 opened a new issue, #45290: URL: https://github.com/apache/airflow/issues/45290
### Apache Airflow version 2.10.4 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? I was using 2.4.1 before and didn't have this problem but after upgrading to 2.10.4 I am facing this problem in my existing DAG. I'm adding parameters to the DAG using Params. When I create a field with the **array** type and specify the element type **number**, the field is rendered as a list on the UI. <img width="704" alt="image" src="https://github.com/user-attachments/assets/a5025127-1c98-44d9-bc6a-50d581b5025b"; /> But when I create the same field with the **array** type but specify the element type **string**, the list is not rendered on the UI and each element must be passed on a new line. I think this is not very convenient and not intuitive. <img width="621" alt="image" src="https://github.com/user-attachments/assets/7dfc5965-62fb-4a7a-971a-b0c3466bc98d"; /> ### What you think should happen instead? I think it would be more convenient if the data type did not affect the way the field is rendered on the UI, and if the array type is specified, then it would be displayed on the UI as a familiar list. ### How to reproduce Code for array with numbers: `params={ "sf_additional_schemas": Param( title="Additional Snowflake schemas", default=[1, 2, 3], type="array", items={ "type": "number" } ),` Code for array with strings: `params={ "sf_additional_schemas": Param( title="Additional Snowflake schemas", default=["schema1"], type="array", items={ "type": "string" } ),` ### Operating System MacOS 15.0 ### Versions of Apache Airflow Providers _No response_ ### Deployment Docker-Compose ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] 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]
