Salsa does not warn or help when passing in wrong argument type

[alexdima]

Testing #2218

/**
 * @param {string} name
 */
function howdy(name) {

}

howdy(3);

even if it knows a string is expected:

[billti]

Correct. We explicitly decided to give no warnings/errors other than syntax errors for JavaScript code. If warnings on incorrect type usage are required, we'd need to spec how and when these would occur in JavaScript, else being based on TypeScript, code such as the below would also be a type error:

var x = 10;
x = "ten";

var y = {a:true};
y.b = false;

[egamma]

In the existing Code JS language service we gave warnings for the first example above and we didn't receive complaints.

We have also warned about undefined variables, which had issues when users where also using a linter in their project and they defined a global as a global in their linter configuration. The confusion was that they define the global in linter configuration, but our JS service still warned about the global.

[egamma]

This issue was moved to microsoft/TypeScript#6658