potiuk commented on issue #28280: URL: https://github.com/apache/airflow/issues/28280#issuecomment-1366424092
HTML and CSS are AWESOME pair. They never case to Amase me. TiL (@uranusjr thanks for finding this gem). Yes, we could canonicalise it. But that would have to be done in backwards incompatibke way if we do - this time we would have to do it in a global way per installation and add some migration to handle all the cases (adding a checkbox of whether to converting would be i guess utterly confusing because almost every one of our users entering the value would have no idea what we are asking them to) My question is - should we rally do something about it or is it mostly academic issue? Do you think @blag this is a real issue that hits our users (what cases?) or is it just the question of treating those behaviours as status quo and maybe just documenting it better ? I personally think that cr/lf confusions has been long enough in many tool that they are handling the confusion well. For example Python when reading string with 'text' parametr will treat the textas containing Universal newlines (that was the deprecated name of this parameter) and in vast majority of case it will **just work** (this is mostly why we have not see this raised as a problem so far). WDYT? Is it worth the hassle of fixing and handling backwards compatibilities @blag? Would you take on such a task if we think it is ? (I think it would have to be done really carefully as some users who actually saw it posaibly apllied already some workarounds to account for that and weight break those workarounds). -- 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]
