iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/.vscode/settings.json

25 lines
666 B
JSON
Raw Normal View History

build: create dist/bin symlink with Bazel outputs (#27781) Note that we had nasty problems in the past when this was enabled, but those have supposedly been fixed. PR Close #27781
2018-12-20 15:12:51 -05:00
{
build: update VSCode settings to limit auto-formatting on save to JS/TS files (#28784) Previously, auto-formatting on save was enabled for all file types, which meant also using default VSCode formatting settings for files where this was not desirable - for example HTML files (such as angular.io and docs examples templates) and JSON files (such as Firebase configurations). This was problematic for the following reasons: - Unlike with JS/TS files, the formatting of other file types is not checked/enforced on CI. - Formatting is subject to default VSCode settings and everyone's local VSCode settings overrides. - Especially for docs examples files, changing the layout might require updating the wording in corresponding guides (e.g. when referring to line-numbers). If we decide that we do want to lint those other file types as well (which sounds like a good idea), we should do it in a way that ensures consistent formatting and check the formatting on CI. PR Close #28784
2019-02-17 08:10:32 -05:00
"[javascript]": {
"editor.formatOnSave": true,
},
"[typescript]": {
"editor.formatOnSave": true,
},
build: update vscode settings to support clang-format (#28348) PR Close #28348
2019-01-24 14:00:52 -05:00
// Please install http://clang.llvm.org/docs/ClangFormat.html in VSCode to take advantage of clang-format
"clang-format.executable": "${workspaceRoot}/node_modules/.bin/clang-format",
build: create dist/bin symlink with Bazel outputs (#27781) Note that we had nasty problems in the past when this was enabled, but those have supposedly been fixed. PR Close #27781
2018-12-20 15:12:51 -05:00
"files.watcherExclude": {
"**/.git/objects/**": true,
"**/.git/subtree-cache/**": true,
"**/node_modules/**": true,
"**/bazel-out/**": true,
"**/dist/**": true,
},
"search.exclude": {
"**/node_modules": true,
"**/bower_components": true,
"**/bazel-out": true,
"**/dist": true,
},
build: show no warning for large git repos (#28055) This warning pops up every time you try to run a node debug session via bazel. It is not important. PR Close #28055
2019-02-08 17:10:19 -05:00
"git.ignoreLimitWarning": true,
build: update VSCode settings to limit auto-formatting on save to JS/TS files (#28784) Previously, auto-formatting on save was enabled for all file types, which meant also using default VSCode formatting settings for files where this was not desirable - for example HTML files (such as angular.io and docs examples templates) and JSON files (such as Firebase configurations). This was problematic for the following reasons: - Unlike with JS/TS files, the formatting of other file types is not checked/enforced on CI. - Formatting is subject to default VSCode settings and everyone's local VSCode settings overrides. - Especially for docs examples files, changing the layout might require updating the wording in corresponding guides (e.g. when referring to line-numbers). If we decide that we do want to lint those other file types as well (which sounds like a good idea), we should do it in a way that ensures consistent formatting and check the formatting on CI. PR Close #28784
2019-02-17 08:10:32 -05:00
}