VS Code settings

[jpa95]

Hi,
We are not using connected mode. We would like to share ObjecScript linting rule configuration between projects. Currently we are setting these configuration at the VS Code USER level, meaning every developper must copy this manually.

Is it possible to save to settings elsewhere than in USER level?

I know that Some extensions look in specific .files.json, that would work great. Also, We are just beginning to use VS Code Workspace files and commit them to git, I have tried but these settings do not seem to be supported at the Workspace level.

In my c:\Users\me\AppData\Roaming\Code\User\settings.json:
"sonarlint.rules": {
"objectscriptquality:OS0028": {
"level": "off"
},
}
I'd like to have that in a file I can commit into git.

[jpa95]

I have tried modifying the settings through the IDE but it seems to only set the configuration in my USERs VSCode Settings.

[jpa95]

In c:\Users\me\.vscode\extensions\litesolutions-es.objectscriptquality-vscode-4.0.1\package.json, I found:

"sonarlint.rules": {
                                "additionalProperties": false,
                                "default": {
                                },
                                "markdownDescription": "Customize applied rule set. This property contains a list of rules whose activation level or parameter values differ from the one provided by default. See _SonarLint Rules_ view for the full list of available rules. In connected mode, this configuration is overridden by the projects's quality profile, as configured on server side.\n\nExample:\n\n    \"sonarlint.rules\": {\n        \"javascript:1481\": {\n            \"level\": \"off\",\n        \"javascript:S103\": {\n            \"level\": \"on\",\n            \"parameters\": {\n                \"maximumLineLength\": \"120\"\n            }\n        }\n    }\n",
                                "order": 1,
                                "patternProperties": {
                                    "^[^:]+:[^:]+$": {
                                        "markdownDescription": "Property names are rule keys in the form: `repo:key`",
                                        "properties": {
                                            "additionalProperties": false,
                                            "level": {
                                                "enum": [
                                                    "off",
                                                    "on"
                                                ],
                                                "markdownDescription": "When set to `off`, disable the rule. When set to `on`, enable the rule.",
                                                "type": "string"
                                            },
                                            "parameters": {
                                                "markdownDescription": "Rule parameters. See rule description for accepted parameters. E.g `{ \"intParam\": \"123\" }`.",
                                                "type": "object"
                                            }
                                        },
                                        "type": "object"
                                    }
                                },
                                "scope": "application",
                                "type": "object"
                            },

"scope": "application" probably explains why this is user-level. Question is can we do something about it?