Cannot suppress diagnostic AL1080 via ruleset.json file

[rvanbekkum]

Cannot suppress diagnostic AL1080 via ruleset.json file

[dannoe]

Just out of curiosity: When is the warning AL1080 generated?

This diagnostic is raised when you use the resourceExposurePolicies property in your app.json file and have allowDebugging set to true while having includeSourceInSymbolFile set to false. This can be reproduced with the example app.json from the original issue description.

See also: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/diagnostics/diagnostic-al1080

And "applyToDevExtension" must be set to true. I've never seen this warning and we use the same settings (except applyToDevExtension).

Can you try to put "suppressWarnings": ["AL1080"] in your app.json?

I can, but that is not what the issue is about and I would rather not apply such a change to tens or hundred of repositories/apps [...]

I was just trying to give the Microsoft guys more information on what might be causing this. I just tested it and suppressWarnings doesn't help either.

[rvanbekkum]

It looks like there has been a recent change somewhere and now compiler diagnostics that used to be only visible in the OUTPUT tab of VS Code are now also visible in the Problems tab.
This would not be a problem for this diagnostic if we had a proper way to suppress it.

[dannoe]

Just out of curiosity: When is the warning AL1080 generated?

Can you try to put "suppressWarnings": ["AL1080"] in your app.json?

[rvanbekkum]

Just out of curiosity: When is the warning AL1080 generated?

This diagnostic is raised when you use the resourceExposurePolicies property in your app.json file and have allowDebugging set to true while having includeSourceInSymbolFile set to false.
This can be reproduced with the example app.json from the original issue description.

See also: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/diagnostics/diagnostic-al1080

Can you try to put "suppressWarnings": ["AL1080"] in your app.json?

I can, but that is not what the issue is about and I would rather not apply such a change to tens or hundred of repositories/apps to avoid it from showing up. With this issue I would like to point out a regression in how/where this diagnostic is raised.
By further investigation I found that with previous versions of ALC this diagnostic would only be shown in the OUTPUT tab in Visual Studio Code, but with the latest versions of ALC this behaviour has changed and diagnostics that would previously only be shown in the OUTPUT tab now also seem to be shown as diagnostics on the app.json file.
(Sidenote: This also happens for diagnostics that are unrelated to the app.json file though.)

[BazookaMusic]

There was a bug where these diagnostics were not being emitted to the problems window and it was fixed. Unfortunately, what seems to not have been fixed is that they are not suppressed properly. Thanks for reporting this

[rvanbekkum]

Thanks for the feedback. 😊