You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Triggering a dag run is a relatively simple process conceptually yet a user is run through multiple different redirects and views. This results in a clunky experience that is slower, causes one to lose context and even end up on a page where they didn't even start on.
Solution:
Handle the API calls within the client and have everything happen within a modal on the user's current page. The modal can handle confirmation events too.
This means that we should copy the logic from the Task Instance modal in dag.html and dag.js, create a new Trigger Dag modal, and update the relevant parts of views.py
The text was updated successfully, but these errors were encountered:
Assigned you @maxnathaniel. I think checking it should be the first thing to do and if you find it's fixed, making a comment about it would be useful as well, so that we can close the ticket :).
@maxnathaniel We should be merging this PR soon, so you could branch off of that and get started. I think the next useful step would be to convert the trigger UI from a separate page to a modal. Like the actions in the graph and gantt views.
@bbovenzi apologies, have been busy with work. Will continue where I had left off with this task this week and aim to push out something by end of week.
Problem:
Triggering a dag run is a relatively simple process conceptually yet a user is run through multiple different redirects and views. This results in a clunky experience that is slower, causes one to lose context and even end up on a page where they didn't even start on.
Solution:
Handle the API calls within the client and have everything happen within a modal on the user's current page. The modal can handle confirmation events too.
This means that we should copy the logic from the Task Instance modal in
dag.html
anddag.js
, create a new Trigger Dag modal, and update the relevant parts ofviews.py
The text was updated successfully, but these errors were encountered: