Skip to content

fix: use same paths as vscode for settings #398

fix: use same paths as vscode for settings

fix: use same paths as vscode for settings #398