Closed jarrodek closed 8 years ago
Hm I assume that if a HTML import can not be resolved, the analyzer can watch that specific location and update accordingly if that location is fixed. I think this is more of a performance analysis than an implementation challenge.
+1, thanks for the bug report. I agree that this is an issue. This is a problem at the editor service level and affects other editors too. Making https://github.com/Polymer/polymer-editor-service/issues/14 the canonical bug.
When the referenced bug is resolved I think it is a good idea to add Atom command to manually refresh the analyser. At the moment I'm having a situation when when the linter shows a warning on an element that the property I just added is not supported by the element. But before adding this attribute I've refreshed bower components and the element and new version has support for this property. Analyser do not know about the change and therefore I'm still seeing the error. If I could run a command to refresh the analyser I would not having this issue.
This is made much more robust by #69.
Worst comes to worst you can reload the atom window with CMD Shift P -> Reload
When I
<link>
import some element that is not present in bower_components directory the plugin will display error as it should. However, after Ibower
this element and it's already available in the path the plugin will continue to display error about missing file. I tried to modify name of imported element and back, remove the line, save and add the line again and nothing changed. After I restarted the editor it finally accept that there's the element.I'm guessing that the information about missing file is cached somewhere and it's not updated after missing file appear. Plugin should inform the analyser that there was a change in files (especially missing files) and should re-run the analysis.