VSCode Compiler errors & Warnings do not appear in VSCode problems tab

[robsrick]

Hey, For some reason I don't get compile warnings or errors listed in the VSCode problems tab. Any ideas why? See video below for a demo.

[Application Ninja]

We need this feature added back in, any further status on this? Why were warnings / errors removed? We need the option to turn on/off at will, please advise...

[Edvin]

I don't think this was ever removed. What missing errors do you refer to?

[Application Ninja]

The problem is exactly as the original posting states, nothing has changed, errors / warnings still do not appear in the "problems" tab...

[Edvin]

Oh, Sorry. I misunderstood. Yes. The build errors have never been part of the problems tab, no. And as far as I know, it is not planned to be. I can add it as a feature request. However, for now you must use the build output. 

Best regards,

Edvin

[Application Ninja]

Hmmm... strange, as others have posted, these warnings / errors had shown in the problems tab before, so this must be a new change / stance on the state of the plugin. Huge inconvenience, so it would be nice to have this added as a feature request as soon as possible...

[robsrick]

+ This definitely used to work and some release of the nrf tooling broke it - whether or not it was intended as a feature.

... but it's hard to understand how this isn't an intentional feature when every other compiler integration with VSCode uses the problemMatchers. Pretty basic feature.

[jonas.woerner]

yes, I also think its a huge inconvenience. its really bad to always have to search the build output if it could be so so so much better.

[Edvin]

What I see is that the Kconfig warnings in the problems tab, for example if I set:

Is that not present in your case? 

[Application Ninja]

Yes, only Kconfig warnings show, but not build warnings / errors of actual C/C++ code...

[Edvin]

So you wouldn't see this?

BR,
Edvin

[Application Ninja]

That's not a build issue of errors reported from the nRF SDK, that's a C/C++ issue as reported from the Microsoft C/C++ extension. So there is a difference in warnings / errors with the nRF sdk vs a C/C++ warning / error. All other MCU's have warnings / errors reported, i.e. Espressif, Silicon Labs, etc... Nordic does not...

[Edvin]

I understand.

Obviously, it is probably difficult for you to show what the build errors used to look like, if you are not seeing them anymore. Do you see them if you roll back to an earlier version of nRF Connect for VS Code?

If not, perhaps you can show an example of what it looks like from one of the other MCUs?

Best regards,

Edvin