Detected the use of
alert, confirm and prompt JS-0052
Anti-pattern
Minor
a year ago
—
a year old
Unexpected alert.
41});
42
43socket.on('signupsuccessful',(msg)=>{
44 alert("SignedUp");45})
46
47socket.on('signuperr',(msg)=>{Unexpected alert.
45})
46
47socket.on('signuperr',(msg)=>{
48 alert(msg);49})
50
51socket.on('msgerr',(err)=>{Unexpected alert.
49})
50
51socket.on('msgerr',(err)=>{
52 alert(err);53});
54
55socket.on('roommsg',(msg)=>{Unexpected alert.
53});
54
55socket.on('roommsg',(msg)=>{
56 alert(msg);57});
58
59socket.on('nameerr',(msg)=>{Unexpected alert.
57});
58
59socket.on('nameerr',(msg)=>{
60 alert(msg);61});
62
63socket.on('autherr',(msg)=>{
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();
}