#2323 Fix enableCodeAnalyzersOnTestApps not disabling customCodeCops in workspace compilation
Workspace compilation now correctly disables custom code analyzers when enableCodeAnalyzersOnTestApps is false, preventing custom analyzer diagnostics from running against test apps.
- 4files
- 2AL files
- 0objects
Pull request · merged into main on 2026-07-21 by aholstrup1 · 4 files (+144 -8), 2 AL · fix · tier official · reviewed (checked by Opus)
What changed
- CustomAnalyzers is now cleared along with Analyzers for test and BCPT test folders when enableCodeAnalyzersOnTestApps is false
- Before, only the built-in cops were disabled and custom analyzer DLLs kept reporting on test apps
- Workspace compilation now matches the documented setting and the classic Run-AlPipeline flow
- Regular apps compile before the test branches, so clearing the shared build parameters there does not affect normal app compilation
- Regression tests check that –customanalyzers is emitted only when custom analyzers are supplied
- Behaviour changes for users or extensions.
AL objects touched
Actions/.Modules/CompileFromWorkspace.psm1: modified, not in the BC? snapshotActions/CompileApps/Compile.ps1: modified, not in the BC? snapshot
Context
- Fixes: #2319 [Bug]:
enableCodeAnalyzersOnTestApps: falsedoes not disablecustomCodeCopsfor test/BCPT apps under Workspace Compilation (CompileAppsaction) (closed) - Systems: development, platform
Source: metadata of a merged pull request in microsoft/AL-Go (al-go): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).