peter-gergely-horvath opened a new issue, #41532:
URL: https://github.com/apache/airflow/issues/41532

   ### What do you see as an issue?
   
   While working with GCP BigQuery operators, I have noticed that some of the 
operators are deprecated. As the message was not prominent enough, first I 
failed to notice it, coded some of my DAGs with the old operators and then 
needed to re-write them so as to avoid deprecated functions. This is not great 
when it comes to documentation UX.
   
   For example: 
https://airflow.apache.org/docs/apache-airflow-providers-google/stable/_api/airflow/providers/google/cloud/operators/bigquery/index.html#airflow.providers.google.cloud.operators.bigquery.BigQueryExecuteQueryOperator
   
   Unless you explicitly double check or look for the deprecation notice, it is 
very easy to overlook it.
   
   
![image](https://github.com/user-attachments/assets/1e6dc85f-ba70-4a8f-869e-f92c2de6b077)
   
   
   ### Solving the problem
   
   I would propose adding the deprecation notice more prominently and changing 
the title background for additional highlighting.
   If we know the operator is deprecated, all it takes is a little bit of CSS 
magic to make it absolutely stand out, say
   
   - Striking the name through
   - Different background color
   - Explicit statement of deprecation in the header
   
   I imagine _something_ like this would be good (at least it is hard to miss 
the point 😊). Again, nothing more than a few lines of CSS should do the trick:
   
   
![image](https://github.com/user-attachments/assets/2c8bbea6-9991-4718-857e-c0098812fb57)
   
   
   
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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