uranusjr commented on PR #24732:
URL: https://github.com/apache/airflow/pull/24732#issuecomment-1174790551

   > That or we could make the API less strict and validate it at the server 
side
   
   Right now the API is very loose and can accept either `tasks`, `task_ids`, 
or even both. And we can still continue to accept `task_ids` (albeit 
deprecated) when we move to OpenAPI 3.1. What is the validation we might need 
you have in mind?


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