Skip to main content
Inline diagnostics show findings right beside your code. The editor underlines the line with a wavy “squiggle” and lists the finding in its Problems panel, so you see an issue while you are editing instead of waiting for a full project report. Each entry has a message and a location you can open.

What is enabled by default

Inline diagnostics are off until you switch them on. Once on, a default set of categories appears: secrets, security smells, @ts-ignore, unused functions and any usage. These are the findings that usually need attention while you edit. Structural warnings, such as a file being too long, stay off. A long file is a property of your project rather than a mistake on one line, and it should not sit beside a type error with the same urgency.

Turning it on

Switch it on for everything in .irisconfig.json, then choose which categories you want:
"enableInlineDiagnostics": false removes every underline and Problems panel entry, while every finding stays visible in the Iris Code sidebar. Nothing stops being detected; it just stops being shown in the editor.