Configuration

ALCops supports several mechanisms to configure which rules are active and how they behave. These mechanisms work across all environments: VS Code, command line, and CI/CD pipelines.

ALCops.json

The ALCops.json file provides analyzer-specific configuration. Place it in the root of your AL project alongside app.json.

{
    "analyzers": {
        "ApplicationCop": {
            "enabled": true
        },
        "LinterCop": {
            "enabled": true
        }
    }
}

Note

The ALCops.json file is read when the analyzer loads. In VS Code, changes to this file require reloading the window (Ctrl+Shift+P → Developer: Reload Window) to take effect.

Ruleset Files (.ruleset.json)

Ruleset files are the standard Microsoft mechanism for configuring diagnostic severity. Create a .ruleset.json file and reference it in your app.json or VS Code settings.

{
    "name": "My Project Ruleset",
    "rules": [
        {
            "id": "AC0001",
            "action": "Warning"
        },
        {
            "id": "LC0007",
            "action": "None"
        },
        {
            "id": "PC0006",
            "action": "Error"
        }
    ]
}

Supported actions:

Action	Effect
`Error`	Treat the diagnostic as a build error.
`Warning`	Treat the diagnostic as a warning (default for most rules).
`Info`	Treat the diagnostic as an informational message.
`Hidden`	Hide the diagnostic but keep it active (visible in code actions).
`None`	Disable the diagnostic entirely.

For full details, see the Microsoft documentation on ruleset files .

Pragma Directives

Use #pragma warning directives to suppress specific diagnostics inline:

#pragma warning disable AC0001
table 50100 MyTable
{
    // AC0001 is suppressed for this block
}
#pragma warning restore AC0001

This is useful for targeted suppression where a ruleset-level change would be too broad.