You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this.context.subscriptions.push(this.analyzer.onDidDetectScript(async(document)=>{/** * @note Provide the full document URI so we apply the schema * both to local and to remote files. */this.scriptPaths.add(document.uri.toString())awaitthis.writeConfigPaths()}),vscode.workspace.onDidDeleteFiles(async(event)=>{for(constfileUriofevent.files){this.scriptPaths.delete(fileUri.toString())}awaitthis.writeConfigPaths()}),)
It appears the onDidDetectScript listener automatically writes new config entries into the yaml.schemas list for each new test file detected. While this is convenient, it is problematic for teams that share settings.json.
Ideally there would be an config option like:
{
"artillery.automaticScriptPaths": false
}
By disabling this, teams could still set artillery.include" & yaml.schemas manually, for example:
From
ArtilleryScriptManager
:It appears the
onDidDetectScript
listener automatically writes new config entries into theyaml.schemas
list for each new test file detected. While this is convenient, it is problematic for teams that sharesettings.json
.Ideally there would be an config option like:
By disabling this, teams could still set
artillery.include"
&yaml.schemas
manually, for example:The text was updated successfully, but these errors were encountered: