Add .vscode to gitignore

[zyusifov]

Change Summary

Description

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist:

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes

[ShahriyarR]

Thanks for PR. But this is desired behavior. We have intentionally added .vscode settings to make developer experience unified. Imagine you have 5 developers who are using VSCode as development tool - if they have similar settings - you are not going to struggle with local settings of each developer.

[asterkin]

@ShahriyarR I was under impression that it's a common practice not to keep IDE configs in git, especially in Open Source projects. Am I wrong?

[ShahriyarR]

@asterkin There are myriad discussions on this topic, some of them prefer ignoring IDE specific folder some of them opt for keeping them, in our case it is useful to keep .vscode/settings.json if some developer wants to be future maintainer to make the development experience as smooth as possible, especially with code server. But yes, it is common to ignore .idea, .atom and .vscode etc, if there are multiple editor settings.

[zyusifov]

Thanks, I guessed that the vscode settings are needed there.