Closed DavidFeldhoff closed 3 years ago
Hi David,
I will take another look. They should behave the same.
Thanks Esben. Appreciate you're looking into it.
The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 27937 and VS Code Extension Version
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read: https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/ https://freddysblog.com/2020/06/25/working-with-artifacts/
1. Describe the bug In reference to https://github.com/microsoft/AL/issues/6700
At the beginning of a file we disable all warnings with "pragma warning disable" If there are AA-Cop-Issues inside the file, the "pragma warning disable" disable all the warnings AND errors If there are AL-Cop-Issues inside the file, the "pragma warning disable" does NOT disable the errors. It only disables warnings. Esben said in the linked issue that it's by design, but I want to ask you to think about it a second time as it's
I don't see any reason why the "compiler cops" (ALxxxx) behave differently than the other cops (CodeCop etc.) and I even do not see a reason why the "pragma warning disable" should not disable warnings which were "updated" to errors.
2. To Reproduce Steps to reproduce the behavior:
3. Expected behavior The pragma warning disable disables the warnings and compiles the file successfully.
4. Actual behavior The file errors due to the AL warnings. If I fix the ALxxx cop issues, so that only the AA-Cop is left which is upgraded to an error as well, then the app compiles successfully as the AA-Error is suppressed.
5. Versions: