I've used both Atom and Visual Studio Code, but in both the same thing always happens eventually:
Even though I'm not doing any updates in the app I'm using at the moment, just coding away (light frontend) as usual, suddenly without any warning the lint just goes haywire and starts warning me about errors that doesn't even exist. Recently it started warning me for files I haven't even touched about images and lack of CSS classes to be missing, but they aren't. They work and the code is 100% correct and have worked before. So I might get 10 various lint errors that are completely false mixed with lint errors that I actually need to fix. Or simply just lint errors that are false.
Again, this happens both in Atom and VSC and it just suddenly happens out of the blue, and this really stuns me. Any ideas why this is and how to correct it?
Related
I'm working on a create-react-app codebase with Typescript enabled.
I find that IDEA real-time syntax analysis of my code often gets "stuck".
I make a mistake, IDEA shows the little red squiggles almost immediately, then I fix the errors but sometimes the red squiggles don't always go away.
For example:
There's nothing wrong with the above code any more, but IDEA still shows the red squiggles, both in the code and the project tool window / changelist window.
I've found that I can "un-stick" the code analysis by killing any/all the node.exe sub-process that IDEA has. Presumably one of those sub-process is "stuck" and when I kill the process, IDEA launches a new one and the syntax error highlighting will disappear.
Obviously, I'd prefer that the code analysis not get stuck at all, but failing that is there a way I can "un-stick" the code analysis from within the IDE?
I'm looking for something faster than re-starting IDEA (or clearing caches, etc.)
Using IntelliJ IDEA 2020.3 (Ultimate edition) on Windows.
package.json configuration and the rest of the code can be found here: https://github.com/kopi-cloud/cabbage/tree/main/app
As per comment from Lena, restarting the Typescript language service will fix issues with stale highlighting errors.
The Typescript status bar widget is usually found at the bottom right of the editor:
Tested with IDEA 2021.1.2
My PhpStorm IDE is giving unresolved variable errors etc for code that is completely fine.
This is happening on stuff such as this.$v, this.$store, this.$auth etc.
Does anyone know how I can fix this? (it will still run perfectly fine, I just find it annoying and harder for debugging)
When I'm using intellij sometimes I do very large refactors that the IDE can't help with. This often breaks a lot of files, but since I'm using either Typescript or Java it's relatively easy to find the problems.
My issue is that I can't seem to get Intellij to check those files unless I open them specifically.
The kind of checking I'm talking about isn't a specific inspection, it's just like the normal compilation problems.
So for example, I have a typescript project and I modified some stuff. When I open some of my React components intellij waits a second, and then highlights parts of it in red. I can go to those parts and see what the issue is.
I've tried forcing the inspector to run, and I've tried building the project, but neither one gives me the red squiggly love I need :^(
It feels like the project->build should force intellij to highlight all this stuff, but it seems to have no effect.
I have a scala project that I'm working on in Intellij. When I opened it up this morning, suddenly none of the code is being analysed properly. The main things I've noticed are that it says every variable is unused (even when it's used in the next line), it doesn't show an error if I try to use a variable that doesn't exist, and I don't get any errors if I try to use a class I haven't imported. TODOs also don't come up in blue.
Does anyone know if there is some sort of setting that somehow could have changed that would affect this? The problem only happens in this one project, all of my other projects are fine.
Edit: I have tried closing it and opening it again, invalidating the cache and restarting and restarting the entire computer.
Edit 2: I forgot to say, if I try to run a test it will come up with the correct compilation errors for things that shouldn't work, but it still doesn't show the error in the code itself.
I'm still not sure why it happened, but I fixed it. I deleted the .idea folder and re-imported the project, and everything was analysed properly.
XCode frequently seems to lose it's mind, and doesn't color code system classes or provide correct "code sense" suggestions. This is endlessly frustrating. The question has been asked on at least three other occasions:
Problems with Xcode Syntax Highlighting
xcode code sense color/completion not working
Xcode: code loses syntax coloring
I have switched by project version to/from 3.1-compatiable and 3.2-compatiable, completely restarting XCode before and after each change with no effect.
I have rebuilt the code sense indexes and completely restarted XCode with no change.
I have built my project to make sure there are no errors and restarted.
I have copied my files (sans .svn files) to a different location - same problem.
I've already completely disabled the argument "placeholders" because they screw up my documents when i type too fast... all I'm asking for is for the "esc" key to display the correct list of properties and methods.
You should clean your project's derived data. They are likely corrupted.
Go to Organizer > Projects > Your_Project > Derived Data > Delete
Xcode will reindex your project and you should be back to normal.
For anyone interested; my app has some precompile directives:
#if ...
Turns out there was an error in one of these sections.
I'm assuming my app built fine because these sections were stripped out before they ever got to the compiler... but CodeSense doesn't care about these (it still wants to color code everything inside these) - so CodeSense would puke all over the place because of the error, even though I didn't find it when I tried to build the app.
Once I fixed the error within that block of code, my coloring returned.
Would be nice if XCode just greyed out those sections instead of dying.