-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(ui/graph): enhance task status visibility #34486
feat(ui/graph): enhance task status visibility #34486
Conversation
Thanks @hainenber Could you provide some before and after screenshots? |
02d1e40
to
50ceb98
Compare
@bbovenzi thanks for the review! I've provided the screenshots in the PR's description and also fixed the linting issue caught during CI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
I'm still a bit stuck on the border color signifying two different things, task state and if its selected. And when I have a selected node, it would become less clear what the status is. One possibility: Don't change the border color on selection, but instead change the node background? |
Co-authored-by: Brent Bovenzi <[email protected]>
Co-authored-by: Brent Bovenzi <[email protected]>
c77b103
to
9be5ca8
Compare
@bbovenzi does this look good to you? 👀 Sorry if it appears I'm nagging you. |
@hainenber much better! One final piece, let's make the border width bigger if the task is selected. and then we can merge this |
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
Closes #34455
Enhance DAG's task visibility by adding border color to task's node and increase size for task's status note.
UI change
Before
After
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.