Enable console.log and alert statements in LWC

-

Hello,

This post is about a very small and somewhat confusing error that you come across when you are doing LWC development. 

Unexpected console statement. eslint(no-console)
Unexpected console statement. eslint(no-alert)

Why does this error occur?
-      This is because ESLint(Linter tool which analyzes code and throws error, when it finds programmatical bugs, syntactical errors, etc.,) considers using console statements or alert statement as a bad practice
-      It is considered as bad practice as console and alert statements are used for debugging purpose and they should not be shipped to the client.

What is the solution?
To overcome this there are 2 ways:
1.   You can disable ESLint’s rule for the whole JS file
export default class accountComponent extends LightningElement {
/* eslint-disable no-console */
/* eslint-disable no-alert */

handleClick(event){
console.log('Event : '+event.target.label);
}
}
2.   You can disable ESLint’s rule for one specific line
export default class accountComponent extends LightningElement {
handleClick(event){
        // eslint-disable-next-line no-console
        console.log('Event : '+event.target.label);
    }
}


This will get rid of the errors. But please be cautious and remove all your console and alert statements before you push your code to the client.

Resources:



Comments

Post a Comment

Popular posts from this blog

SFDX Push Error : An object 'ComponentName' of type LightningComponentBundle was named in package.xml, but was not found in zipped directory

-
Image
 Hello, Nowadays salesforce developers have moved to SFDX and VSCode as their primary IDE. There is one error which has particularly bothered me and my team.  This error occurs when you create a new SFDX project and retrieve all the components, do all the required changes lets say in a lightning web component and try to push the component to salesforce org. This error occurs :  An object 'ComponentName' of type LightningComponentBundle was named in package.xml, but was not found in zipped directory. Solution: Please do check if there is meta.xml file in the component bundle, this error occurs because of missing meta.xml file. For some weird reason, the meta.xml file is not retrieved with the component. If that is the case, then one solution is to create a meta.xml file manually under the component folder with the general XML configuration as below: <? xml  version = "1.0"  encoding = "UTF-8" ?> < LightningComponentBundle   xmlns = "http://soap....
Read more

Salesforce Apex Triggers Interview Questions/Scenarios

-
 Hello, This post is regarding some apex trigger interview questions. These questions are for Novice to Intermediate level developers. I feel these questions/scenarios would be helpful for practice. PS: The questions below are collected from the internet and some of them are which I was asked in the interviews I appeared for. 1.    Create "Sales Rep" field with the datatype (Text) on the Account object. When we create an Account record, the Account's owner name will be automatically added to the sales rep field. When we update the Account owner of the record, then also the Sales Rep will be automatically updated. 2.    Create a field called "Contact Relationship"(checkbox) on the contact object and create the object called "Contact Relationship" which is related to Contacts (Lookup Relationship). Now build a logic when we create contact by checking the Contact Relationship checkbox, a Contact Relationship record will be created automatically for that c...
Read more