-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
Rework Params UI Tutorial DAG #47265
Rework Params UI Tutorial DAG #47265
Conversation
f175332
to
cfd5e91
Compare
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.
PR Overview
This PR refactors the Params UI Tutorial DAG to improve the form UI by consolidating parameters and organizing them into clearer sections.
- Renames parameter keys to be more descriptive (e.g. changing "x" to "number_param").
- Adds section attributes to group parameters by type and functionality.
- Introduces additional parameters (boolean, date/time, required/optional text fields) to broaden form functionality.
Reviewed Changes
File | Description |
---|---|
airflow/example_dags/example_params_ui_tutorial.py | Parameter keys are renamed and reorganized into sections to improve UI clarity and form usability. |
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (2)
airflow/example_dags/example_params_ui_tutorial.py:83
- Consider renaming the parameter key 'bool' to a more descriptive name (e.g., 'confirm_param') to avoid confusion with Python's built-in bool type.
"bool": Param(
airflow/example_dags/example_params_ui_tutorial.py:207
- [nitpick] Consider renaming the section to a more concise and standard title, such as 'Advanced Form Fields', for clarity.
section="Special advanced stuff with form fields",
006dcf0
to
75e7813
Compare
3753b5e
to
740b051
Compare
Co-authored-by: Copilot <[email protected]>
740b051
to
7ccf877
Compare
@eladkal can you re-review? Or shall I ask somebody else? |
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.
LGTM
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.
LGTM
I noticed that the Params UI Tutorial DAG had quite a lengthy list of parameters... and as the new trigger form is a modal it was hard to see all values.
I consolidated a few fields and added more form sections to make the view better.
FYI @shubhamraj-git