[Feature]: Global alcops.json

[IceOnly]

Problem / motivation

We have company rules that applied on all our apps.

Proposed solution

A global alcops.json would solve this issue for use. It would be nice if the extension tries to parse in this order:

• Global
• Workspace
• App

Alternatives considered

No response

Additional context

No response

[MODUSCarstenScholling]

Isn't that like #500 ? Does that new feature already cover your request?

[IceOnly]

Ohh this will help. But I would like to have a setting in vscode with my defaults.

[someC0d3r]

Ohh, this will help. But I would like to have a setting in VS Code with my defaults.

Just to add some context here: I made a similar suggestion in the LinterCop repository a while ago:
StefanMaron/BusinessCentral.LinterCop#1134

I think the main challenge was roughly this:
LinterCop also runs outside of VS Code, for example when alc.exe is called directly in CI/CD pipelines. In that scenario, VS Code's configuration system is not available - the compiler only works with the app folder.

While LinterCop could technically read .vscode/settings.json, VS Code settings can also be defined at user or workspace level. Those settings would not be available when compiling outside of VS Code.

This could therefore lead to different LinterCop behavior locally in VS Code compared to the pipeline.

A dedicated LinterCop.json avoids that problem by providing a single, predictable configuration source that works independently of the editor.

[Arthurvdv]

There’s also #329, where I now see that this didn’t make it into the documentation.

I’ve updated the Configuration page on alcops.dev, which now covers both options under “Where alcops.json is loaded from” to include the #329.

As @someC0d3r already mentioned, I don’t have much insight into the VS Code side from an ALCops perspective. The analyzers also need to work in pipelines, MCP, and other environments outside VS Code. But there options available, is this something you could work with @IceOnly?