Hi 👋 — a heads-up for the CA Rules Viewer / analyzer handling.
BusinessCentral.LinterCop is deprecated. Development has moved to its successor, ALCops, and users are asked to migrate before October 2026.
al-code-outline currently references the LinterCop analyzer by name in a couple of places, e.g.:
vscode-extension/src/carulesviewer/caRulesCollection.ts (the BusinessCentral.LinterCop.dll entry)language-server/Shared.AnZwDev.ALTools/CodeAnalysis/CodeAnalyzersLibrariesCollection.cs (same)
It would be great if the tooling recognized ALCops so its rules surface in the CA Rules Viewer going forward.
I'm the maintainer of ALCops and I'm happy to open a PR for this if that's welcome — just let me know how you'd prefer the analyzer to be wired in (naming/architecture is your call). Thanks for al-code-outline! 🙏
Hi 👋 — a heads-up for the CA Rules Viewer / analyzer handling.
BusinessCentral.LinterCop is deprecated. Development has moved to its successor, ALCops, and users are asked to migrate before October 2026.
al-code-outline currently references the LinterCop analyzer by name in a couple of places, e.g.:
vscode-extension/src/carulesviewer/caRulesCollection.ts(theBusinessCentral.LinterCop.dllentry)language-server/Shared.AnZwDev.ALTools/CodeAnalysis/CodeAnalyzersLibrariesCollection.cs(same)It would be great if the tooling recognized ALCops so its rules surface in the CA Rules Viewer going forward.
I'm the maintainer of ALCops and I'm happy to open a PR for this if that's welcome — just let me know how you'd prefer the analyzer to be wired in (naming/architecture is your call). Thanks for al-code-outline! 🙏