Open MattTraxinger opened 2 months ago
Hello Matt, thanks for bringing this to our attention. I see you are using version 15.0.1129943, which is a pre-release version of the AL extension, and that this happens in BC 25.0 which as of right now is also in public preview.
May I ask if you are seeing a similar issue when using the latest non-prerelease version of the extension too? I'll reach out privately too, if you would like to share the repository in which this happens.
I've reached back out via email to share the repo.
This is specifically to address issues with the next major release, so I have use BC25 symbols. I can only download those from the environment using the AL Language v15 extension. The earlier versions of the AL Language don't seem to be compatible. I can't even try to compile the app with an earlier version.
I'm just following up on this as I provided the repo a while ago.
1. Describe the bug I have an app that I am compiling against the next major release. The compiler output (not the problems window, but the actual compiler output) does not show all errors in the app. I have confirmed this is not specific to certain Cops being turned on or custom rulesets as the behavior happens when nothing is turned on.
2. To Reproduce I'm happy to privately share the repository where this is happening. I am simply compiling, either is VS Code or directly with the compiler via BcContainerHelper.
3. Expected behavior All errors should be shown in the compiler output.
4. Actual behavior Here is the problems tab, which contains all errors and matches the Microsoft email (36 errors)
Here is the compiler output (5 errors):
And the matching pipeline output (5 errors):
When all 5 errors are corrected, I get the remaining 31 in the compiler output. The same ones included in the Microsoft email. Here are a few:
5. Versions: