fix(ux): no confirmation dialog when deleting a plugin from form

[vanshaj2023]

Issue description

Clicking the Delete button on a plugin card inside a form (Routes, Services, Plugin Configs, etc.) immediately removes the plugin with no confirmation. There is no way to undo this — the user must re-add and re-configure the plugin from scratch.

Current behavior
onDelete?.(name) is called directly in onClick with no guard:
https://github.com/apache/apisix-dashboard/blob/master/src/components/form-slice/FormItemPlugins/PluginCard.tsx#L81

Expected behavior

A confirmation dialog should appear before deleting, consistent with how top-level resources are deleted (DeleteResourceBtn uses modals.openConfirmModal).

How to Reproduce

1. Go to Plugin Configs → Add Plugin Config
2. Add any plugin (e.g. response-rewrite) and configure it
3. Click Delete on the plugin card
4. Plugin is deleted instantly — no confirmation dialog

Screenshots

Apache.APISIX.Dashboard.-.Personal.-.Microsoft.Edge.2026-03-21.04-30-07.mp4

Environment

• apisix-dashboard: master

Additional context

No response

[vanshaj2023]

Hi @Baoyuantop ,
I noticed that clicking Delete on a plugin card immediately removes it with no confirmation, which can cause accidental data loss. Would you like me to fix this?
I can wrap the delete call in modals.openConfirmModal, same pattern already used in DeleteResourceBtn.tsx.

[Jaswanth-arjun]

Hi @vanshaj2023, I would like to work on this issue.

I am planning to add a confirmation dialog before deleting a plugin, similar to DeleteResourceBtn using modals.openConfirmModal, to ensure consistent UX across the dashboard.

Please let me know if this approach is fine or if any specific behavior is expected.

[Jaswanth-arjun]

Hi @vanshaj2023 , I have worked on this issue and opened a PR:

#3345

This PR adds a confirmation dialog before deleting a plugin to prevent accidental removal and aligns with existing UX patterns.

Please review when possible. Thanks!

[vanshaj2023]

Hi @Jaswanth-arjun ,
Thanks for the pr. But it is not the right way of contribution you have to first wait for the reply or assignment then start working. Please read contribution.md.

[utkarshsingh1102]

Hi @vanshaj2023 ,

I’d like to take up issue #3342 (missing confirmation dialog when deleting a plugin from the form).

My proposed approach:

1. Introduce a confirmation modal in PluginCard.tsx using modals.openConfirmModal
2. Extract a handleDelete function to trigger the modal
3. Ensure onDelete?.(name) is only executed inside onConfirm
4. Keep the modal configuration consistent with DeleteResourceBtn (same confirmProps and i18n keys like info.delete.title, info.delete.content, etc.)

This will align plugin deletion UX with existing resource deletion behavior and prevent accidental removals.

Please let me know if this approach works or if you'd prefer any adjustments before I proceed.

Thanks!

[Jaswanth-arjun]

Thank you @vanshaj2023 for your guidence, As a beginer i dont know full details about how to contribute,As i fixed already bug what should i do now.

[vanshaj2023]

Hi @Baoyuantop
Please review this issue.
I think we must add confirmation here.
Do I start working and submit a pr regarding this?

[Jaswanth-arjun]

Hlo @vanshaj2023 it mean the current issue #3342 not assigned to me?where i already submitted PR #3345.

[vanshaj2023]

Hi @Jaswanth-arjun ,
I just say wait for maintainers confirmation then fix the issues.

[Baoyuantop]

I don’t think this feature is necessary. Since we’re currently on the data creation page rather than the edit page, removing the plugin simply deletes it from the data being created—it has no impact on active configurations. Therefore, there’s no need for this additional confirmation.

[vanshaj2023]

Hi @Baoyuantop,
Thanks for the clarification.
Do we have to keep this issue open to fix later, or should we just close the issue?