This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 486764 - [eslint] Consume no-implicit-coercion rule
Summary: [eslint] Consume no-implicit-coercion rule
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: JS Tools (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 13.0   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-28 13:14 EST by Michael Rennie CLA
Modified: 2016-07-21 12:01 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 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 CLA 2016-07-19 13:59:36 EDT 
For the first draft, I won't support in orion the allow property.
Comment 2 Olivier Thomann CLA 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 CLA 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 CLA 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.