fix: Adjust flow cascade deletion and improve flow delete message UI #6667
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 pull request includes changes to both the backend and frontend of the application to improve the handling and display of flow data. The most important changes include updating the cascade delete functionality, modifying modal behavior based on flow types, and ensuring proper deletion warnings are displayed.
Backend changes:
src/backend/base/langflow/api/utils.py
: Added import forMessageTable
and updated thecascade_delete_flow
function to ensure messages are deleted when a flow is deleted. [1] [2]Frontend changes:
src/frontend/src/pages/MainPage/components/grid/index.tsx
: ModifieddescriptionModal
to differentiate between components and flows, and added a note to the delete confirmation modal to warn users about message deletion when deleting a flow. [1] [2]src/frontend/src/pages/MainPage/components/list/index.tsx
: Similar changes to the grid component, ensuring thedescriptionModal
differentiates between components and flows, and added a deletion warning note. [1] [2]#5925
https://discord.com/channels/1116803230643527710/1338862961841799179