Option to stop extension from creating .vscode folder in workspace

[ghost]

Even if I'm not using git at all, the Prisma extension creates a .vscode/settings.json file in my workspace with the following settings:

{
    "files.watcherExclude": {
        "**/.git/objects/**": true,
        "**/.git/subtree-cache/**": true,
        "**/.hg/store/**": true
    }
}

If I remove the .vscode folder, the extension recreates it. Is there a reason for this?

[janpio]

I can confirm this behavior. Creating a new project with prisma init and then opening the schema in VSCode with the extension is enough to get these 4 lines added to your .vscode/settings.json (or the file being created if it does not exist yet).

[carmenberndt]

Hi @joaopaulobdac!

This issue was fixed in #443.

What happened: To be able to solve the problem of hanging types, our solution was to restart the TS Language Server on every change to node_modules/.prisma/client/index.d.ts. In order to detect changes to this file, we had to change the workspace settings, otherwise changes to node_modules were ignored by default. This unfortunately lead to the creation of the .vscode/settings.json file.

We now are detecting changes with a different file watcher (chokidar), which does detect changes to the node_modules folder. Therefore no settings will be changed on your side anymore, and also no .vscode/settings.json file will be created.

Please try out 2.6.0 and let us know if there are any issue with it.

[ghost]

Thanks for describing what was happening behind the scenes! I already upgraded to 2.6.0, no more settings modifications here.