f07a642eb9
Update VS Code to support *.code-snippets
2021-12-10 10:59:08 +09:00
8be0bf6f8f
Make not to ignore *.code-workspace
...
**Reasons for making this change:**
Workspace file can allow you to have an individual VS Code setting file for each project, which is useful for monorepo-based development.
You can find an example on [lit/lit/lit-next.code-workspace](08f60328ab/lit-next.code-workspacehttps://code.visualstudio.com/docs/editor/multi-root-workspaces#_workspace-file
2021-09-18 17:12:32 +09:00
eefa65c924
Ignore Local History folder ( #3008 )
...
This will add support for the default location the Local History extension for Visual Studio Code uses.
See https://marketplace.visualstudio.com/items?itemName=xyz.local-history
2020-04-04 13:30:38 -03:00
21419e391a
Update to Global/VisualStudioCode ( #3201 )
...
Added ignore for workspace files (*.code-workspace). They can be added in any directory, depending on the user's preferences.
2019-10-10 14:32:23 -03:00
3e303c561b
Modified VS Code .gitignore
...
Added extensions.json as exception in .vscode folder. File is used as
extensions recommendation for project.
2016-11-21 14:04:42 +01:00
554bccef40
Update Visual Studio Code to support workspace files.
...
Visual Studio Code has a few files that can be placed into the workspace
in order to share settings across users. Settings.json is for project
specific overrides. Tasks.json is for executable tasks (build, gulp, etc.)
While launch.json is for debugging specific tasks.
2016-08-04 22:29:32 -07:00
ed7d67a175
VSCode 0.8.0 config folder change
...
Starting with 0.8.0, VS Code will store its settings in a .vscode folder and no longer in the generic .settings folder.
2015-08-31 09:39:54 +02:00
db9ef4a789
Move VS Code to Global folder
2015-05-02 10:56:11 +03:00
Tim