Repository navigation
Add import error to deactivated dag - #65687
Conversation
pierrejeambrun
left a comment
There was a problem hiding this comment.
Thanks, looks cool.
A few suggestions
65d6d59 to
55c7ed3
Compare
55c7ed3 to
6c072e5
Compare
d944902 to
e766863
Compare
|
A bunch of updates. I refactored the whole thing to be a banner on the HeaderCard that will display on any Dag related header |
parkhojeong
left a comment
There was a problem hiding this comment.
Thanks, looks good overall.
I left one comment about multi-bundle import error matching.
9bb9a9a to
52f1848
Compare
jscheffl
left a comment
There was a problem hiding this comment.
Cool from my side! Definitely helps fiding errors more quickly.
Just one UX question: Why not using the same Banner we have for Backfill and in general for this? Would be a bit more consistent.
I want to redo that banner to be honest. |
52f1848 to
194bd6f
Compare
f7a0f9e to
59c883f
Compare
# This is the 1st commit message: Add import error to dag page when deactivated # This is the commit message #2: Move to modal
59c883f to
1a21010
Compare
* # This is a combination of 2 commits. # This is the 1st commit message: Add import error to dag page when deactivated # This is the commit message apache#2: Move to modal * Add import error to dag page when deactivated * Change badge to a banner * Fix test * Cleanup banner code * Add bundleName param * Fix CI
When a dag is stale, check for import errors and display any.
I switched this to a banner in the HeaderCard instead of in the dag breadcrumb. Helps handle deactivated dags and if they have any import errors.
Related #56250
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.