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

Bug 486764

Summary:	[eslint] Consume no-implicit-coercion rule
Product:	[ECD] Orion	Reporter:	Michael Rennie <Michael_Rennie>
Component:	JS Tools	Assignee:	Olivier Thomann <Olivier_Thomann>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Olivier_Thomann
Version:	unspecified
Target Milestone:	13.0
Hardware:	All
OS:	All
Whiteboard:

Description Michael Rennie

2016-01-28 13:14:28 EST

We should consume the no-implicit-coercion rule

http://eslint.org/docs/rules/no-implicit-coercion

Comment 1 Olivier Thomann

2016-07-19 13:59:36 EDT

For the first draft, I won't support in orion the allow property.

Comment 2 Olivier Thomann

2016-07-19 14:01:06 EDT

Neither I will have support for "number", "string" and "boolean". All implicit coercion will be reported.

Comment 3 Olivier Thomann

2016-07-21 09:54:45 EDT

Ok, with the addition of dependent preferences, I will have support for number, string and boolean. The allow property has been added for 3.0.1. So I will add that support later.

Comment 4 Olivier Thomann

2016-07-21 12:01:05 EDT

Delivered as commit http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=7bc3c8014d07b82c6e0dbcfac1813c136a90baea.

I didn't add a quickfix for now. I am updating the eslint wiki page.