I'm trying out AppCode for a simple Swift iOS application, and the first thing I noticed is it won't highlight any error whatsoever. The build fails with simple errors like use of unresolved identifier 'param', but it won't highlight to let me know said variable doesn't exist. Moreover, the the file analysis (little green checkmark at top-right corner) says No problem found.
I'm using AppCode 2016.1
Do I have to make some kind of extra configuration or similar?
Showing warnings and errors in editor is not yet implemented in AppCode 2016.1 for Swift. This feature is ready in AppCode 2016.2 Early Access Preview. Download it here and in case you interested in updates - read about it in our blog
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
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 updated the Xcode to 8.3 version today, but I found a new error message, a gray exclamation mark. I do not know what it means, But the program can run normally. Does anyone know what this symbol means?
That error style is not new to Xcode 8.3, but your project may be experiencing new warnings or errors due to changes in Xcode 8.3 which is causing this style to appear.
That style is used to provide you with additional information about a given error or warning. You should see the primary issue somewhere above the grey exclamation mark style. There should also be a disclosure triangle that will let you collapse this additional information.
You need to resolve the primary issue.
It really annoys me that IntelliJ highlights certain 'errors' (that don't prevent successful compilation) the same way that real errors are highlighted. For example, a magic number is not really an error, but it will be flagged in exactly the same way as an incompatible type error.
How can I change this?
Go to Settings -> Inspections. Then you need to search through the long list for the offending inspection, which you can get the name of by hovering on the warning marker in the margin. You can change the severity of the inspection, whether it's an error, warning, etc. or just disable it altogether.
Edit: if you search for "magic" in Settings, you get the following, which should be helpful:
Whenever you see an inspection warning/error you can place the caret on it and press Alt+Enter (a light bulb also appears that tells you that). A menu will appear with suggested quick fixes. You may need to open a submenu by pressing Right, and you'll find "Edit inspection settings" there. Having invoked that, you may proceed as in hvgotcodes's answer :), it's just a faster way of getting to those settings.
As Michael Calvin said you can use the SuppressWarnings annotation. For example:
#SuppressWarnings("OptionalUsedAsFieldOrParameterType")
See https://github.com/JetBrains/intellij-community/blob/master/plugins/InspectionGadgets/src/inspectionDescriptions/OptionalUsedAsFieldOrParameterType.html
Usually searching the internet for the exact description leads me to this.
Not directly relevant to the OP, but may be of use to future Googlers
I got to this question while trying to figure out how to disable IntelliJ IDEA's warnings about Guava functionalities that have been replaced by Java 8 features. I'm not able to use the Java 8 versions of these features in my case because of a library we're using that was built with Guava (despite being a Java 8 project). So to solve that, I added a SuppressWarnings annotation before any class using Guava:
#SuppressWarnings(Guava)
public final class...
Everywhere there are pretty pictures of failing tests shown inline in the code editor, like in Peepcodes Objective-C for Rubyist screencast and in apples own technical documentation:
(source: apple.com)
When I build my test-target, all I get is a little red icon down in the right corner, stating something went wrong. When clicking on it, I get the Build Results, where I can start to hunt for test results.
Do anyone have a clue on what´s wrong?
Have a look at your Xcode preferences. Under the Building tab you want to change your settings for Message Bubbles.
This works for Xcode 3.1 which it looks like the image you've shown. Xcode 3.2 has a different style of bubble and doesn't have this preference.
Press "Cmd =" to travel between build results, you should see a warning.
Also, that specific warning seems like it's from the static analyzer - you turn that on by going to project preferences and checkmarking "run static analyzer" or by using the "Build and Analyze" option.
Try Cmd-Shift-H to show all message bubbles.