kacpermuda commented on code in PR #37075: URL: https://github.com/apache/airflow/pull/37075#discussion_r1470781860
########## docs/spelling_wordlist.txt: ########## @@ -122,6 +122,7 @@ avp Avro avro aws +AwsBaseAsyncHook Review Comment: In the doc page we are providing instructions on what a user should use instead of a deprecated entity, so it's usually a message with path or name of another Airflow class,method, function etc. So i think yes, it may happen that with every build there might be a new "unknown" word if there is a new deprecation and new class included in the deprecation message. I am not sure if there is a way to avoid it? Developers can put anything in the deprecation message and it may cause spelling checks to fail, but it should be caught in the PR that adds the deprecation. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
