karenbraganz opened a new issue, #67359:
URL: https://github.com/apache/airflow/issues/67359

   ### Description
   
   The window displaying the dag code in the Airflow UI has become smaller in 
Airflow 3.2 and harder to read from.
   
   On Airflow 3.1:
   
   <img width="1470" height="735" alt="Image" 
src="https://github.com/user-attachments/assets/521d41f8-ffe7-4d47-881c-97db51c7aa71";
 />
   
   On Airflow 3.2:
   
   <img width="1450" height="742" alt="Image" 
src="https://github.com/user-attachments/assets/2a16b706-6f4e-487b-9c8a-065d38707dd4";
 />
   
   It would be great if we could expand this code view to the entire screen for 
readability. 
   
   A feature to filter the dag code for keywords or at least use cmd/ctrl+F 
would be helpful for troubleshooting. On Airflow 3.1, we could use cmd/ctrl+F 
to search for keywords in the dag code even if those words were not on the 
screen without scrolling. In Airflow 3.2, only the words visible in the small 
window will be highlighted with cmd/ctrl+F.
   
   For example, here I am running cmd+F for the word "instantiate", and it 
shows 0 matches.
   
   <img width="1471" height="750" alt="Image" 
src="https://github.com/user-attachments/assets/ab7edf4f-9706-4fe0-9538-635582fea612";
 />
   
   Only when I scroll to the bottom of this code where this word is present 
will it detect a match.
   
   <img width="1457" height="729" alt="Image" 
src="https://github.com/user-attachments/assets/9e6c4499-8e5d-4715-b138-8bcbc291e55c";
 />
   
   This was not the case in Airflow 3.1.
   
   
   ### Use case/motivation
   
   This feature would improve code readability on the UI.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a 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