technopahadi opened a new issue, #27228: URL: https://github.com/apache/airflow/issues/27228
### Apache Airflow version Other Airflow 2 version (please specify below) ### What happened Airflow Version Used: 2.3.3 This bug report is being created out of the following discussion - https://github.com/apache/airflow/discussions/25064 With the following DAG definition (with nested params): ``` DAG( dag_id="some_id", start_date=datetime(2021, 1, 1), catchup=False, doc_md=__doc__, schedule_interval=None, params={ "accounts": Param( [{'name': 'account_name_1', 'country': 'usa'}], schema = { "type": "array", "minItems": 1, "items": { "type": "object", "default": {"name": "account_name_1", "country": "usa"}, "properties": { "name": {"type": "string"}, "country": {"type": "string"}, }, "required": ["name", "country"] }, } ), } ) ``` **Note:** It does not matter whether `Param` and JSONSchema is used or not, I mean you can try to put a simple nested object too. Then the UI displays the following: ``` { "accounts": null } ``` ### What you think should happen instead Following is what the UI should display instead: ``` { "accounts": [ { "name": "account_name_1", "country": "usa" } ] } ``` ### How to reproduce _No response_ ### Operating System Debian Linux ### Versions of Apache Airflow Providers _No response_ ### Deployment Composer ### Deployment details Although I am personally using Composer, it is most likely related to Airflow only given there are more non-Composer folks facing this (from the discussion's original author and the Slack community). ### Anything else I have put some more explanation and a quick way to reproduce this [as a comment in the discussion](https://github.com/apache/airflow/discussions/25064#discussioncomment-3907974) linked. ### 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]
