jscheffl commented on issue #36369: URL: https://github.com/apache/airflow/issues/36369#issuecomment-1878544655
Hi @mblakely Can you tell me a bit more details about your use case and motivation "why" you want to have a boolan and "null" value as union option? The UI can only render (today) a element which generates true/false - but a user can not select "null" - therefore during implementation this was not considered. What I am thinking is whether this use case is really needed and UI needs to support it (==bug) or if it is not a valid use case that we rather generate a parsing warning (==missing feature). Reason why the UI behaves like this today is that it checks for type==boolean (which it is not in your example) to decide for a on/off option, if no other specific type matches, it falls back to a string entry field and therefore generates a string. To add more complexity to my initial question, what also is not covered might be the case of `type=["boolean", "string"]` which also would fall-back to string but this time it would be valid. -- 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]
