Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 485169

Summary: [eslint] Upstream no-eq-null rule returns bad message sometimes
Product: [ECD] Orion Reporter: Michael Rennie <Michael_Rennie>
Component: JS ToolsAssignee: Michael Rennie <Michael_Rennie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 11.0   
Target Milestone: 11.0   
Hardware: All   
OS: All   
Whiteboard:

Description Michael Rennie CLA 2016-01-04 13:19:13 EST 
Consider the following snippet:

if(myvar != null) {
 //do something
}

the entire expression will be flagged with the message reading: "Use '===' to compare to 'null'".

The message should read "Use '!==' to compare to 'null'" and only the offending operator should be marked.