"Cannot find controller" marker doesn't disappear when expected

[fbricon]

This is a corner case, but I'm reporting it anyways :

• create a web project with angularjs nature
• create a new index.html page and copy the content of the index.html page of the todo example in https://angularjs.org/
• "Cannot find controller" error markers appear for ng-app and ng-controller attributes, since the todo.js file, declaring the expected objects, doesn't exist yet
• create a new todo.js file and copy the content of the todo.js page of the todo example in https://angularjs.org/. Save the file. => the error markers should disappear from index.html but they don't. A dummy change in index.html will force revalidation and fix the problem.

[angelozerr]

I agree with you, it should be better that revalidation should be done in this case.

But it means that you must refresh the whole HTML files which are opened in an editor when any JS files are changed? What is about performance? You could use script element to know dependency between HTML and JS files, but it will not work with requirejs.

In other words, this issue seems a little complex although I think some other issues should be done at first (like managing completion inside JS for templateUrl (HTML files))

But any PR are welcome!