<p dir="auto">In 0.10.8, if I have a TypeScript Definition for a JavaScript file, there is validation done on the parameters. This was particularly useful for finding broken APIs.</p>
<p dir="auto">Example of definition file and code:<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/7843164/13714107/8da20336-e79a-11e5-87e5-8a3164caabec.png"><img src="https://cloud.githubusercontent.com/assets/7843164/13714107/8da20336-e79a-11e5-87e5-8a3164caabec.png" alt="image" style="max-width: 100%;"></a></p>
<p dir="auto">In 0.10.8, a warning is shown for an incorrect type:<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/7843164/13714116/9f7416f8-e79a-11e5-9063-7b0ed08021f5.png"><img src="https://cloud.githubusercontent.com/assets/7843164/13714116/9f7416f8-e79a-11e5-9063-7b0ed08021f5.png" alt="image" style="max-width: 100%;"></a></p>
<p dir="auto">Now, in 0.10.10, there is no validation at all. The "100" shows as being valid:</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/7843164/13714176/0722b250-e79b-11e5-9cf5-c353ab67501c.png"><img src="https://cloud.githubusercontent.com/assets/7843164/13714176/0722b250-e79b-11e5-9cf5-c353ab67501c.png" alt="image" style="max-width: 100%;"></a></p>
<p dir="auto">Losing the validation is a big loss. When switching to Salsa, was this the intention? Is there any properties that can be set to have the JavaScript intellisense + validation go back to the old engine (I believe it was using the TypeScript engine).</p>
<p dir="auto">Thanks</p>
<p dir="auto">See <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="129227097" data-permission-text="Title is private" data-url="https://github.com/microsoft/TypeScript/issues/6658" data-hovercard-type="issue" data-hovercard-url="/microsoft/TypeScript/issues/6658/hovercard" href="https://github.com/microsoft/TypeScript/issues/6658">#6658</a> for background.</p>
<p dir="auto">Currently for JavaScript files we provide a very limited set of errors, mostly for syntax errors. There are a number of grammatical and type errors that would be useful to display also.</p>
<p dir="auto">Brief notes from ad hoc discussion in the team room include:</p>
<ul dir="auto">
<li>Move the code that flags TypeScript syntax in JavaScript files for better error handling</li>
<li>Add a distinction between errors and warnings to avoid "valid" JavaScript containing errors</li>
<li>Make the warnings user configurable as part of the project (i.e. may enable/disable certain warnings)</li>
</ul>
<p dir="auto">More detailed design to come...</p>