potiuk commented on PR #26486: URL: https://github.com/apache/airflow/pull/26486#issuecomment-1319411447
As you wish - I still don't think that this is only part of the problem and changing it here changes literally nothing, because we are mixing both styles everywhere, but if you feel better about it - no problem. Note - I never "requested changes" here, I just stated my opjnion that this does not treat the root cause of the problem which is that we have hell of a mess when it comes to our examples and no consistent approach for it and that we are not bringing consistency and not removing confusion by this change - instead, at most, we just don't give a chance to a user who wants to find out what airflow is by a quick glance, to understand that they can write DAGs in much more modern way as well. But if I am just one person who thinks that way - I am certainly not dying on that hill. I just hope that the refactor of the structure will happen sooner rather than later and that we will be able to get a better chance to change the perception of our docs as well. I just read a comment about Airflow docs that it is "freaking abysmal" and well, to be honest, it kinda is. Hopefully we can make it consistent in both - structure and approach and consistent message to the users, rather than keep on the current "band-aid over band-aid approach". I just have a rule that whenever I see a problem I try to fix it "in general" rather than in single place when I know there are other places with the same problem - because it pretty much always leads to even more mess, but I do not have the bandwidh to do it now unfortunately. -- 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]
