dsuhinin opened a new pull request, #76018:
URL: https://github.com/apache/airflow/pull/76018

   Prototype for the direction discussed in #45290 ("a small PR to test the 
outcome").                                                                      
                                                                                
                                                                                
 
                                                                                
                                                                                
                                                                                
                                                                               
    An array param currently renders as three different widgets depending on 
the element type: a multiline textarea for string items, a JSON editor for 
number items, a multiselect when `enum`/`examples` are present. The textarea 
path also silently converts untyped array elements to strings on submit (`[1, 
2, 3]` becomes `["1", "2", "3"]`) and accepts empty entries, while element 
validation only exists in the JSON editor and only for numbers and objects. 
With this change, arrays with string / number / integer / boolean / untyped 
elements share a single chips input:                                            
                                                                                
                                                                                
                                                                          
     - Enter (or Tab) adds an element, pasting multiline text adds one chip per 
line —                                                                          
                                                                                
                                                                               
       so the "one value per line" entry flow is preserved, no JSON required    
                                                                                
                                                                                
                                                                               
     - each entry is validated against `items.type` in place; invalid entries 
are                                                                             
                                                                                
                                                                                
 
       rejected with an inline error instead of being submitted                 
                                                                                
                                                                                
                                                                               
     - element types are preserved for untyped arrays
   
   Behaviour before changes:
   
   <img width="911" height="1387" alt="Screenshot 2026-10-29 at 13 02 28" 
src="https://github.com/user-attachments/assets/e8d6707a-6f04-41ce-abbf-6527580e7e7a";
 />
   
   New implementation:
   <img width="895" height="1237" alt="Screenshot 2026-10-30 at 09 18 40" 
src="https://github.com/user-attachments/assets/0a777b6a-630a-44b0-a7fe-9cf2e2f3f688";
 />
   <img width="898" height="1246" alt="Screenshot 2026-10-30 at 09 18 59" 
src="https://github.com/user-attachments/assets/ef5067d9-a59d-4d2b-b48e-08dd379f1a34";
 />
   <img width="898" height="1244" alt="Screenshot 2026-10-30 at 09 19 22" 
src="https://github.com/user-attachments/assets/f855412e-f7dc-4437-9694-b62b341d5f65";
 />
   <img width="897" height="1242" alt="Screenshot 2026-10-30 at 09 19 31" 
src="https://github.com/user-attachments/assets/671d4753-05a0-470f-9f98-34ad2823e158";
 />
   


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