Show missing interface method implementation as error in project view
I would like to know whether it is possible (and if yes how :)) to see missing interface method implementation in project view.
So the implementing class will be marked the same way like when you make a typo...
Like this:

If i create an interface and a class that implements this interface and later add a method definition into the interface, implementing classes that do not implement the method, are not marked as problematic:

Please sign in to leave a comment.
Hi there,
>So the implementing class will be marked the same way like when you make a typo...
It's not a typo there. Typo is Spellchecker-related and has lowest severity/priority. What you see there is a parser error (highest severity), which is serious and not suppressible hence it's shown even in Project tree.
But in general:
Yes you are correct about the parser and thank you for the pointers to Inspections.
When i do "Code | Inspect Code" i get the error in the inspection results. However I like to have these errors visible in the project tree structure because it's more visual (and am used to it from other IDE :) )
I tried to change the inspections based on the error i get from Inspect Code, however even if i set it as Error, it's not underlined in project view.
Setting:
Based on this error:
No idea what else to set as error to make this work ...
I've mentioned "Code | Inspect Code" as possible alternative for time being -- if you need to see all serious errors it allows you to see all of them + in one place.
The benefit is: it analyses your file even if it's not currently opened / was opened recently.
With error highlighting in Project tree -- if you do not have that file open (so IDE does not really know about those issues) it will not highlight that file -- at very least that's how it works for CSS files (e.g. imaging some 3rd party .css file that uses some browser hacks or alike that IDE is unaware/fails to accept as valid. As long as I do not open such file in current session IDE does not show any red underwaves for that file. But once I have to open it -- that annoying/distracting for me highlighting is shows (annoying as I cannot resolve it myself -- that code must remain as is)).
Ok, that makes sense. Thank you for your answers!
I'll use the Inspections results for now.