Repository navigation
Made the Visual Studio Code Configuration Sharable - #19
Merged
Merged
Conversation
Added the Workspace Config+ extension by Swellaby, which allows developers to share Visual Studio Code configuration as `.shared.json` files and each developer may add custom `.local.json` files. The extension automatically merges the shared and local files. This way core configuration settings can be shared and each developer may make local changes to these settings without overriding other's settings. I deleted the original `.vscode/settings.json` and replaced it with a shared version (`.vsocde/settings.shared.json`). I removed the file nesting and the VSCode Icons configuration from it, because it is not something that is not something all developers may want to have. These configuration settings now live in my personal `.vscode/settings.local.json` settings. Also, the Workspace Config+ extension was added to the `.vscode/extensions.json`, so that it gets recommended to all developers working on the project. Since the Visual Studio Code settings still contained a branch protection for `staging`, which is now called `development`, the branch was corrected also.
lecode-official
added
the
Type: Idea or Request
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added the Workspace Config+ extension by Swellaby, which allows developers to share Visual Studio Code configuration as
.shared.jsonfiles and each developer may add custom.local.jsonfiles. The extension automatically merges the shared and local files. This way core configuration settings can be shared and each developer may make local changes to these settings without overriding other's settings.I deleted the original
.vscode/settings.jsonand replaced it with a shared version (.vsocde/settings.shared.json). I removed the file nesting and the VSCode Icons configuration from it, because it is not something that is not something all developers may want to have. These configuration settings now live in my personal.vscode/settings.local.jsonsettings. Also, the Workspace Config+ extension was added to the.vscode/extensions.json, so that it gets recommended to all developers working on the project.Since the Visual Studio Code settings still contained a branch protection for
staging, which is now calleddevelopment, the branch was corrected also.Closes issue #18.