Unwanted settings added

[ddnexus]

Every time you interact with the extension it authoritatively creates this in the settings.json:

    "files.exclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/CVS": true,
        "**/.DS_Store": true,
        "**/.*": true
    },

While the latter is my own setup, why it adds the others? 🧐

[JeremyFunk]

The former elements are hidden by VSCode by default. The way hide files works is by overwriting files.exclude with all your hidden files. It is restoring the original files.exclude (the VSCode default setting) and appending all your defined files to the end every time you make changes to the hidden files list.

I plan to release hide files V3 with some major under the hood reworks at the end of this month/early next month. It will include a JSON setting to override this.

[SkyCodeSky]

Are there any news yet? I really would like to toggle on and of the .git folder. 😊

[JeremyFunk]

V3 will have to wait a bit, not sure exactly when I will find time. I will release a minor version with only this feature added tomorrow, as this has been requested quite a few times. I have created a section in the Readme to explain what exactly you have to do (it will purely be a setting, no fancy UI for now).

[riolly]

It would be great if the config is not in .vscode/settings.json @JeremyFunk
So that we can add it on .gitignore

[zoey-kaiser]

+1 on this! Would love to use it, but sadly we push our settings.json on git. @JeremyFunk do you have an idea on how you would want to implement this? If yes, I would not mind looking into pushing this in my free time!

I would propose the following approach:

• Allow the configuration of profiles in the .vscode/settings.json folder, so it can be shared between team members
• Save the files.exclude in another file inside the .vscode folder, which can then be .gitignored. Naming could be hidefiles.local.json or something else

Is this also what you would propose? Otherwise feel free to present an alternative and I could then follow that approach 😊

Also super nice for you to know and maybe advertise this extension: Inside the Nuxt ecosystem a discussion recently surfaced about managing config files in a more organized manner.
The proposal in this case was to add .config folder to Nuxt itself, which would then compile any config files inside, as if they were in the root. This solution would work for config files, such as the nuxt config, tailwindconfig etc. But sadly it would not cover files such as the .gitignore or .tsconfig.json, which is where I think your extension could really fill that void.

You can find the proposal here: https://github.com/pi0/config-dir

If we manage to get this issue solved, I think you extension would cover this issue REALLY well. I would also bring this up, but sadly this issue here is blocking me from recommending it further!

let me know if I can help in any way and what the next steps would be ❤️