Closed kevin-mueller closed 2 years ago
Works well. I noticed another minor particularity. It seems like the extension load classes from a) any .css class in the project (which is not a razor.css) b) any isolated css classes (for example Index.razor.css for Index.razor) I accidentally made a typo and the isolated css file was not case-sensitive compared to the page (index.razor.css with a lower case "i")... This file's classes were not scanned. IDK right now, how default VS behavior in general is for such wrong-case isolated classes or code-behind files, but at least the solution explorer visually seems to recognize them correctly. I'd consider it a mistake/bad practice not the match case here, anyway, but it's simply sth i noticed. (IDK if that has implications in other places, but if not, and if VS in general accepts different casing here, it would be more consistent if the extension would do that also.)
You're right, case should be ignored when checking for isolated context. Issue tracked here: #7
Fixed in version 1.11 @AMUCOMO
When renaming or deleting a CSS class, the suggestion stays in the cache, even if manually re-scanned.