Migrating from BusinessCentral.LinterCop

The BusinessCentral.LinterCop project has been the foundation for community-driven AL code analysis and it’s rules and diagnostics are now part of ALCops

• ApplicationCop covers application conventions, labels, permissions, and UX standards.
• DocumentationCop covers comments, XML documentation, and code documentation.
• FormattingCop covers code style, formatting, and visual consistency.
• LinterCop covers code quality metrics, complexity, and modern AL patterns.
• PlatformCop covers platform-level correctness, runtime safety, and API constraints.
• TestAutomationCop covers test code structure and correctness.

If you are currently using the BusinessCentral.LinterCop, use the mapping below to find where each diagnostic moved.

Diagnostic Mapping

Entries marked with — do not have a new diagnostic ID assigned (yet).

Notable Changes

Rules split into multiple diagnostics. LC0009 and LC0010 each covered both cyclomatic complexity and maintainability index. In ALCops these are separate diagnostics (LC0007/LC0009 and LC0008/LC0010 respectively) so you can control each metric independently.

Rules merged. LC0003 and LC0012 both flagged the use of hardcoded object IDs. They are consolidated into LC0003 .

Rules split across analyzers. LC0044 (TransferFields matching) is now covered by two PlatformCop diagnostics: PC0020 and PC0021 .

Updating Your Ruleset

If you maintain a custom .ruleset.json that references LinterCop rule IDs, update the IDs to match the new analyzer prefixes. For example:

{
    "rules": [
        {
            "id": "PC0001",
            "action": "Warning",
            "justification": "Previously LC0001"
        },
        {
            "id": "AC0001",
            "action": "Warning",
            "justification": "Previously LC0004"
        }
    ]
}

Any pragma directives in your AL code (#pragma warning disable LCxxxx) need to be updated to the new diagnostic IDs as well.