techolga commented on issue #41019:
URL: https://github.com/apache/airflow/issues/41019#issuecomment-2265947375

   Hi,
   I introduced the change of the UI element in `2.9.3`. with 
60243e77ddf1ecea2aad524cebbd174fb03d40f5. The JSON input element was previously 
shown on simple string arrays because of a bug in the template. I was not aware 
of the side effect it has on the handling of an empty array as default, but I 
think now it conforms 
[AIP-50](https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-50+Trigger+DAG+UI+Extension+with+Flexible+User+Form+Concept).
   
   > - Type of the field derived from the JSON schema type and formatting clause
   >     * Type boolean can render a checkbox or on/off control
   >     * Elements of JSON format date and date-time can render a date picker
   >      * Type of arrays can be made as lists of text string and object types 
as a JSON sub-element entry
   > - If JSON schema allows to have types of null can control if a field is 
optional or required.
   
   As far as I understand the current mechanism of the trigger page it looks 
like this:
   
   1. the default value is inserted into UI input element, if the element is 
not a sequence nothing is inserted (what else should we do with an empty list 
as default value?)
   2. the content of the input element is extracted and displayed in the 
`Generated Configuration JSON` element (how should we now distinguish between 
an empty array and null?)
   
   At the moment I do not see a clever way to handle this edge case with the 
current structure...


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