Add Trigger DAG UI with advance options - #43367
Conversation
|
@jscheffl Tried to cover many points. Still some points left.
|
jscheffl
left a comment
There was a problem hiding this comment.
Some early bird comments - mostly beautifying and details. Don't take all of them too serious, rather as hints.
98d83cf to
042947b
Compare
bbovenzi
left a comment
There was a problem hiding this comment.
Let's move this from inside components/DataTable to components/TriggerDag
2fad497 to
e910c44
Compare
|
Oh you already rebased? How was moving your changes to chakra v3? |
|
@bbovenzi |
|
Ok. Let me know if you want me to pull the branch down and help with the rebase. |
e910c44 to
a9104d6
Compare
jscheffl
left a comment
There was a problem hiding this comment.
Just one small bug and a small nit... otherwise looks very good and from my point could be merged!
Thanks!
bbovenzi
left a comment
There was a problem hiding this comment.
Great work! Thanks for being patient with all the back-and-forth review comments.
+1 from my side for handling all the comments :-D |
* Initial draft * some modifications * rectifications * initial react hook * reset only on form change * moving to diff componnent * upgrading chakra ui 3.0 for TriggerDagForm.tsx * upgrading chakra ui 3.0 for TriggerDagModal.tsx * fix lint * fix css * add close * dynamic theme for json * lint fix * simplify reset * reviews * json validation * remove color schema * use accordion * Add Accordion component * Use accordion component in triggeer form * remove dag id from title * fix response tracking * add blue button * making diff components for diff buttons * lints * lints fix * variant add * reset the form on close * change type to string * optimise * post input validation and pretiffy for json * modal refactor * reviews * add fiplay button * replace logical with data interval * add dag pause-upause toggle * enable trigger for pause dag * refactor * DAG --------- Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com>
^ 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.rstor{issue_number}.significant.rst, in newsfragments.