Home/ Questions/Q 6381837
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T02:26:43+00:00

I have the following working code : var routes = []; Eclipse validator for

  • 0

I have the following working code :

var routes = [];

Eclipse validator for javascript prints the following warning :

Type mismatch: cannot convert from any[] to any

What is wrong with my empty array ?

Edit : the warning disappeared later. Apparently Eclipse was wrong and the question needs to be closed. Sorry about that.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Your JavaScript is valid, the problem is with JSDT plugin for Eclipse. In the latest version they introduced a type verification which is problematic in many situations – not only for empty arrays (like in your case). Another typical case may look like this: a = b || c;
    The plugin will complain when b and c are of different types (which is absolutely valid code for JavaScript). There is several bugs already reported to JSDT developers about this problem, but the issues are not fixed yet.

    Unfortunately currently it is not possible to switch off the type verification using JSDT configuration screen in Eclipse. I switched it off directly from the JSDT source code. To do this, please follow these steps:

    1. Download the JSDT source code from Eclipse WebTools Project
    2. Open the org.eclipse.wst.jsdt.debug.core project with Eclipse. Make sure you have Eclipse SDK installed. It might also be required to adjust some dependencies in the plugin.xml file.
    3. The type verification is located in computeSeverity method of ProblemReporter class.
    4. To switch off type verification replace the line: case IProblem.TypeMismatch: return ProblemSeverities.Warning; with case IProblem.TypeMismatch: return ProblemSeverities.Ignore;
    5. Build the project and close Eclipse.
    6. In Eclipse folder find the file named org.eclipse.wst.jsdt.core<version>.jar – make a safe copy of it, then open the jar file and replace the ProblemReporter.class file with the one you compiled in the step 5 (the file is in bin folder of your project).
    7. Start Eclipse and clean your JavaScript project. All type checking will be ignored by JSDT.

    Important! Make sure you’ve downloaded the same version of JSDT that you are using in Eclipse. Eventually instead of replacing a single file you can replace the entire plugin.

    If you don’t want to download and compile the plugin by yourself you can try with my fixed version. I’ve placed it on my FunctionSack webpage. I am using Eclipse 3.7 (Indigo) with JSDT 1.3.0, so make sure you have similar configuration if you want to use my file.

    • 0