Use VSCode Settings Instead of a Separate LinterCop.json File for Configuration

[someC0d3r]

Something like this:

Advantages:

• Settings can be configured at the user, workspace (*.code-workspace), or app-specific level (app/.vscode/settings.json)
• No need to keep in mind and modify pipelines for the individual file as needed settings can be read from (see above) app-specific settings if set

• Aligns more closely with how other VSCode extensions work
• Settings can be adjusted via the VSCode Settings UI

---

Is there a specific reason for using a separate file instead of leveraging the built-in VSCode settings?
It seems like using the native VSCode settings would be a better approach. :-/

[jwikman]

I believe that the reason is that LinterCop should work also outside of VSCode, when calling alc.exe directly (as in pipelines).

[someC0d3r]

Hmm, could LinterCop read from /.vscode/settings.json instead of a separate /LinterCop.json when fetching rule settings? Maybe I'm oversimplifying, but since both are just JSON files in the app directory, what makes one accessible and not the other? 😢

[jwikman]

LinterCop could (probably) read from the /.vscode/settings.json as a fallback, if /LinterCop.json is not found.

But it cannot read the settings from a workspace file, since the compiler is run on a folder - not a workspace.

I don't know if a VSCode setting can be configured to only be available in .vscode/settings.json and not in the workspace.

If that is possible, I think this could be a nice approach.
If not, having settings that are available in the workspace, but only works when in VSCode, and not when compiling, I would vote for not doing this.

In the docs for the settings, in the scope section on Configuration property schema, it seems as this is not possible.

I believe that resource is the only viable option here, and it also make the setting available at workspace level... 😕

But please correct me if I'm wrong!