Detected the use of
alert, confirm and prompt JS-0052
Anti-pattern
Minor
5 months ago
—
5 months old
Unexpected alert
83function sendInfoMail() {
84 Inertia.get('/admin/email/sendBeforeBITMailToAllUsers');
85 showInfoMailModal.value = false;
86 alert("Emails wurden versendet");87}
88
89Unexpected alert
77function sendReminderMail() {
78 Inertia.get('/admin/email/sendDecisionReminderMailToAllUsers');
79 showReminderModal.value = false;
80 alert("Emails wurden versendet");81}
82
83function sendInfoMail() {Unexpected alert
71function sendLinkToAllUsers() {
72 Inertia.get('/admin/email/sendLoginLinkMailToAllUsers');
73 showAnmeldeLinkModal.value = false;
74 alert("Emails wurden versendet");75}
76
77function sendReminderMail() {Unexpected alert
71
72function resetBIT() {
73 Inertia.get('/admin/reset');
74 alert('BIT-Seite wurde zurückgesetzt!')75}
76
77</script>
Description
JavaScript's alert, confirm and prompt functions are widely considered to be obtrusive as UI elements and should be replaced by a more appropriate custom UI implementation.
Furthermore, alert is often used while debugging code, which should be removed before deployment to production.
Bad Practice
alert("here!");
confirm("Are you sure?");
prompt("What is your name?", "John Doe");
Recommended
customAlert("Something happened!");
customConfirm("Are you sure?");
customPrompt("Who are you?");
function foo() {
const alert = myCustomLib.customAlert;
alert();
}