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.
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
In my IntelliJ editor, I am facing this trouble that randomly some files becomes invisible to other files using them.
I have tried refreshing the workspace and even rebuilding the project but error won't go away even though the build never complains, the problem would suddenly disappear for a file and reappear for others.
When class is available it should not give red squiggly lines in the editor as it hampers in other code editing tasks.
I found the solution to this problem it's simple
goto File | then select invalidate cache and restart option, it resolved the issue, answering.
While editing a JavaScript file, the IDE shows highlights on the lines that have problems and displays the lightbulb when you're on one of those lines.
How can I see a live list of all problems found in the current file (e.g. syntax errors)?
The only way I found so far was to manually run inspection and check the inspection window. That's quite cumbersome. Even the "Problems" section of the Project window updates itself automatically as soon as I change the code (even without saving) - but it doesn't display the actual errors (only which files have errors).
Apparently the IDE knows what errors exist in the file - I just can't find a way to see all of them in a list.
In every other IDE I know, it is a built-in, enabled-by-default, feature: eclipse, visual studio, brackets, etc.
Apparently this is an open issue on the IntelliJ family of products. Please upvote that issue if you feel it is missing as well!
Hi there i am trying to learn more about Griffon, but using IntelliJ it seems that code completion is not correct and variables are not recognized. So i am surely doing something wrong. I have created a new Griffon project and various things are not recognized. Also when i try to add a MenuBar for example code completion seems not to work. When i run it everything seems ok! So what am i missing???
It's a known Griffon bug fixed for 0.9.5.
The Griffon library manages the intellisense by itself, and, unfortunately, in this version it's broken. You can fix it by opening griffon.gdsl file, copying it into your project (or editing in-place and repacking into the jar), fixing two unclosed string literal problems there, and re-activating the script using the link at the top of the editor. This would bring you code completion.
Another option is to wait for Griffon 0.9.5 release or try the snapshot build.
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.