potiuk commented on PR #30981:
URL: https://github.com/apache/airflow/pull/30981#issuecomment-1538856638

   Just for backwards compatibility sake, I would do it differently. I'd rather 
add another parameter (`messages_str` maybe ?) and an option to add encoding 
(defaulting to "utf-8") possibly  The old way of doing it still might be done 
and  the way it is proposed it causes a warning to be always printed when you 
use "regular" string. We should never get to the sistuation where you use a a 
valid parameter that causes a warning that you should ignore. It is very bad 
from usability point of view.
   
   Adding new parameter which will be equally easy to use as templated field 
solves the problem, and keeps backwards compatibility while does not introduce 
this cumbersome warning.


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