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

Bug 495208

Summary:	[eslint] Remove the check-tern-project rule
Product:	[ECD] Orion	Reporter:	Michael Rennie <Michael_Rennie>
Component:	JS Tools	Assignee:	Michael Rennie <Michael_Rennie>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	12.0
Target Milestone:	12.0
Hardware:	PC
OS:	Mac OS X
Whiteboard:

Description Michael Rennie

2016-06-01 14:02:31 EDT

As part of bug 487279 we added a linting rule that would nag the user if the current file they were editing was part of their .tern-project file (as a loadEagerly entry).

Over the last month (or so) of us playing with and ignoring the nagging rule, we should get rid of it. It does not help the end user, is annoying, is set to 'ignore' by default, and can cause Tern to chew up a tonne of (possibly unused) memory if the user applied the fix for every file they opened.

Comment 1 Michael Rennie

2016-06-01 15:42:30 EDT

Fixed in:

http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=17ab616a9bdcdc018846839d1dbcc70808dd6955

Updated the wiki as well