[Feature] Local Workspace settings
I would like to be able to configure settings that are specific to my user and to a particular workspace. So, 'local' workspace settings? So there would be three locations for settings (for a single-folder workspace): * user settings * `${workspaceRoot}/.vscode/settings.json` * `${workspaceRoot}/.vscode/settings.local.json` This way, I can add `.vscode/settings.json` to git, and share project settings such as "exclude node_modules" but I can gitignore `.vscode/settings.local.json` and add things specific to that project that I don't want to share, such as git autofetch. I originally thought to suggest `.vscode/settings.user.json`, similar to how VS Pro handles similar configuration, but that might be confusing.
Posted by firelizzard18 on Dec 14, 2017, 10:18 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
[Feature] Local Workspace settings
I would like to be able to configure settings that are specific to my user and to a particular workspace. So, 'local' workspace settings? So there would be three locations for settings (for a single-folder workspace): * user settings * `${workspaceRoot}/.vscode/settings.json` * `${workspaceRoot}/.vscode/settings.local.json` This way, I can add `.vscode/settings.json` to git, and share project settings such as "exclude node_modules" but I can gitignore `.vscode/settings.local.json` and add things specific to that project that I don't want to share, such as git autofetch. I originally thought to suggest `.vscode/settings.user.json`, similar to how VS Pro handles similar configuration, but that might be confusing.
Comments (0)
No comments yet. Start the discussion.