-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Hide logical date and run id in trigger UI form #35284
Merged
jscheffl
merged 9 commits into
apache:main
from
boschglobal:feature/hide-logical-date-and-run-id-in-trigger
Nov 8, 2023
Merged
Hide logical date and run id in trigger UI form #35284
jscheffl
merged 9 commits into
apache:main
from
boschglobal:feature/hide-logical-date-and-run-id-in-trigger
Nov 8, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jscheffl
requested review from
ryanahamilton,
ashb,
bbovenzi,
pierrejeambrun and
potiuk
as code owners
October 30, 2023 22:56
boring-cyborg
bot
added
area:UI
Related to UI/UX. For Frontend Developers.
area:webserver
Webserver related Issues
kind:documentation
labels
Oct 30, 2023
jscheffl
changed the title
Feature/hide logical date and run id in trigger
Hide logical date and run id in trigger UI form
Oct 30, 2023
I like it. No good knowledge to comment on the code, but the ideas here are good. |
eladkal
approved these changes
Nov 1, 2023
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.
Nice!
Nice. Thanks @jscheffl 👍 |
Congraulations on your first (!?) merged PR as committer @jscheffl :D |
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Nov 10, 2023
* Move Run ID and Logical Date into hidden section, layout fixes * Make DAG docs display per default in trigger DAG UI * Update UI Screenshot in docs * Add form elements to legacy form as well --------- Co-authored-by: Jens Scheffler <95105677+jens-scheffler-bosch@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:UI
Related to UI/UX. For Frontend Developers.
area:webserver
Webserver related Issues
kind:documentation
type:improvement
Changelog: Improvements
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is an improvement based on the feedback raised in issue #34726 and optimizes the layout of the trigger UI form.
This PR changes:
AIRFLOW__WEBSERVER__SHOW_TRIGGER_FORM_IF_NO_PARAMS=True
is setHow to test?
example_params_ui_tutorial
and check the formAIRFLOW__WEBSERVER__SHOW_TRIGGER_FORM_IF_NO_PARAMS=True
and trigger the DAGexample_python_operator
with configUI Before:
UI After:
DAG Options when un-folded lower section:
closes: #34726