Refactor notifications with toasts and modals

[sven1103]

What are you missing?

Success notifications (Toasts)

Usage: Triggered after successful completion of each task

• Project creation and editing
• Experiment creation and editing
• Experimental variables creation and editing
• Experimental groups creation and editing
• Offer upload and remove
• QC upload and remove
• PAT token creation, copying and deletion
• Project Access person add and remove (also email notifications for the same)
• Show toast on Sample batch add, update, remove #973
• Sample batch dialog add, remove row
• Show toast on measurement interaction #977
• Measurements - RAW data available

Warning notifications (Dialogs)

Usage: To warn the user of potential risks that may arise during an interaction.

• Confirmation msgs on delete Sample batch
• Confirmation msgs on delete PAT
• Confirmation msgs on delete measurement

Information notifications (Dialogs)
Confirmation msg on dialog cancellation

• cancel project creation
• cancel project editing
• cancel experiment creation
• cancel experiment editing
• cancel exp. variable creation
• cancel exp. variable editing
• cancel sample batch registration
• PAT copy
• TSV conversion in dialogs (Register and Edit measurements)

Error Notifications

Usage: To inform users of critical issues and guide them to resolution.

• File upload : exceeding size, improper TSV, technical errors (DB, network, etc)
• Editing experiment design after samples are registered.
• Deleting measurements when no item is selected.

Why do you need a solution?

Depends on #682

Ideas

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[wow-such-code]

Is cancel confirmation for experimental groups missing by design?

[Shraddha0903]

Is cancel confirmation for experimental groups missing by design?

@wow-such-code Yes, we don't have the cancel confirmation for the experimental groups by design as imo the accidental action of the Cancel button is not potentially as harmful as the others. The lost information could cost the users not more than a few minutes to reenter compared to the increased amount of clicks caused by the cancel confirmation that would annoy them.
We should keep them only for the dialogs where the action could be destructive and would cost some time and effort to the user. We should also remove it for the sample batch registration dialog, as there won't be the spreadsheet component anymore.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.