-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Field Deletion Warning when editing Connections #41144
Conversation
@lh5844 can you also add a unit test please? |
Because I've kept the general warning and that change is made in the connection_form.js, there don't seem to be any unit tests for any javascript files. So, I'll leave it at that. Correct if I'm wrong though |
…irflow into edit_connection_message
One last comment. Otherwise lgtm! |
Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com>
Thank you for your suggestion! It definitely made it more concise. With that, it should be ready to be merged! |
* able to change the 'Changed Row' display message after edit * added message in connection form to warn of empty fields * attempt to warn the specific fields cannot be empty * revert change because need to check fields before save is clicked * issues warning for specific fields that can't be deleted after save * removed the individual warnings * changed status to concise string * added more concise suggestion Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com> --------- Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com>
* able to change the 'Changed Row' display message after edit * added message in connection form to warn of empty fields * attempt to warn the specific fields cannot be empty * revert change because need to check fields before save is clicked * issues warning for specific fields that can't be deleted after save * removed the individual warnings * changed status to concise string * added more concise suggestion Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com> --------- Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com>
* able to change the 'Changed Row' display message after edit * added message in connection form to warn of empty fields * attempt to warn the specific fields cannot be empty * revert change because need to check fields before save is clicked * issues warning for specific fields that can't be deleted after save * removed the individual warnings * changed status to concise string * added more concise suggestion Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com> --------- Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com>
* able to change the 'Changed Row' display message after edit * added message in connection form to warn of empty fields * attempt to warn the specific fields cannot be empty * revert change because need to check fields before save is clicked * issues warning for specific fields that can't be deleted after save * removed the individual warnings * changed status to concise string * added more concise suggestion Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com> --------- Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com>
* able to change the 'Changed Row' display message after edit * added message in connection form to warn of empty fields * attempt to warn the specific fields cannot be empty * revert change because need to check fields before save is clicked * issues warning for specific fields that can't be deleted after save * removed the individual warnings * changed status to concise string * added more concise suggestion --------- Co-authored-by: Lucy Hu <90779522+lh5844@users.noreply.github.com>
* able to change the 'Changed Row' display message after edit * added message in connection form to warn of empty fields * attempt to warn the specific fields cannot be empty * revert change because need to check fields before save is clicked * issues warning for specific fields that can't be deleted after save * removed the individual warnings * changed status to concise string * added more concise suggestion Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com> --------- Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com>
* able to change the 'Changed Row' display message after edit * added message in connection form to warn of empty fields * attempt to warn the specific fields cannot be empty * revert change because need to check fields before save is clicked * issues warning for specific fields that can't be deleted after save * removed the individual warnings * changed status to concise string * added more concise suggestion Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com> --------- Co-authored-by: Brent Bovenzi <brent.bovenzi@gmail.com>
* able to change the 'Changed Row' display message after edit * added message in connection form to warn of empty fields * attempt to warn the specific fields cannot be empty * revert change because need to check fields before save is clicked * issues warning for specific fields that can't be deleted after save * removed the individual warnings * changed status to concise string * added more concise suggestion --------- Co-authored-by: Lucy Hu <90779522+lh5844@users.noreply.github.com>
The issue mentions that fields backed by the BS3TextFieldWidget cannot be deleted once populated. To delete those fields, the user must delete the connection and create a new one. The "Changed Row" message displayed after a row is edited is misleading.
Therefore, as a temporary fix, I have created a warning that always shows when the user is editing a connection form as shown below.
What I tried to do was get the specific fields that were populated and issue a warning with those field names when the user tries to delete them. However, I'm having trouble figuring out how to do that check when the user clicks the 'Save' button. So, I have a warning of the currently populated fields that can be modified but not deleted after the user clicks 'Save' shown below.
related: #40105
^ 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.rst
or{issue_number}.significant.rst
, in newsfragments.