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

Bug 486365

Summary:	[eslint] no-console rule should be ignore
Product:	[ECD] Orion	Reporter:	Michael Rennie <Michael_Rennie>
Component:	JS Tools	Assignee:	Michael Rennie <Michael_Rennie>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	P3	CC:	steve_northover
Version:	11.0
Target Milestone:	11.0
Hardware:	All
OS:	All
Whiteboard:

Description Michael Rennie

2016-01-22 10:17:39 EST

The no-console rule should be turned down a bit to be a warning by default. Long gone are the days when there is no console object available in browsers, so a gentle reminder (via a warning) that you might not want to leave debugging statements in your code would be better.

Comment 1 Steve Northover

2016-01-22 10:27:57 EST

Mike, can you just fix this to make it no longer a warning?  As a data point from memory, I think that JDT does not warn for System.out so we should likely do the same.

Comment 2 Michael Rennie

2016-01-22 10:32:15 EST

(In reply to Steve Northover from comment #1)
> Mike, can you just fix this to make it no longer a warning?  As a data point
> from memory, I think that JDT does not warn for System.out so we should
> likely do the same.

Good point. I updated the bug summary to reflect this.

Comment 3 Michael Rennie

2016-01-22 10:35:59 EST

Fix in http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=02fa7a8521774026928ea9ca4cf12090e19914a0

This fix will not change the severity in workspaces that have changed the pref from the default.

I also updated the wiki:

https://wiki.eclipse.org/Orion/ESLint#Potential_Programming_Problems