Expected '===' and instead saw '=='. (eqeqeq)

[BSravanthi]

It is considered good practice to use the type-safe equality operators === and !== instead of their regular counterparts == and !=. The reason for this is that == and != do type coercion which follows the rather obscure Abstract Equality Comparison Algorithm. For instance, the following statements are all considered true: [] == false [] == ![] 3 == "03" If one of those occurs in an innocent-looking statement such as a == b the actual problem is very difficult to spot. You can choose the equlityStyle you prefer, either "smart" or "allow-null"

"smart" This option enforces the use of === and !== except for these cases:
    Comparing two literal values
    Evaluating the value of typeof
    Comparing against null

"allow-null" This option will enforce === and !== in your code with one exception - it permits comparing to null to check for null or undefined in a single expression.

//Smart:
//Good:
	typeof foo === 'undefined'
	'hello' !== 'world'
	0 === 0
	true === true
	foo === null
//Bad:
	a == b 
	foo == true
	bananas != 1
	value == undefined

Please refer to the following link to fix similar issues.
https://app.codacy.com/app/BSravanthi/pattern-recognition-iiith/issues?&filters=W3siaWQiOiJMYW5ndWFnZSIsInZhbHVlcyI6W251bGxdfSx7ImlkIjoiQ2F0ZWdvcnkiLCJ2YWx1ZXMiOlsiRXJyb3IgUHJvbmUiXX0seyJpZCI6IkxldmVsIiwidmFsdWVzIjpbbnVsbF19LHsiaWQiOiJQYXR0ZXJuIiwidmFsdWVzIjpbMTY2MV19LHsiaWQiOiJBdXRob3IiLCJ2YWx1ZXMiOltudWxsXX0seyJ2YWx1ZXMiOltdfV0=

[DevikaBoddu]

Commit id: c2a2881-exp2
Commit id: 903d72f-exp5
Commit id: a1ae248-exp7

[ShivaniKomandury]

Commit id : 0075c8b
Commit id : 127f2e9
Commit id : a39dc2a

Please validate.

[VINEETHREDDYSHERI]

Valid fix @ShivaniKomandury

[snehitharangu]

Valid fix @ShivaniKomandury

[somashekhar31]

validated-2 fix @ShivaniKomandury

[somashekhar31]

commit id:ce23792

[kasyapbhuvanagiri]

commit id: 9ad2c6f