langfingaz/anki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
8504bd67ed
anki/.vscode/settings.json

24 lines
806 B
JSON
Raw Normal View History

add vscode conf so pylib imports resolve in aqt by default
2022-01-21 12:50:53 +01:00
{
add some more VS Code workspace settings for Python/Rust
2022-01-23 07:39:40 +01:00
"editor.formatOnSave": true,
switch convenience symlinks to .bazel/ Unfortunately 5efaf5a4be95e289210e964a5cd40b4f08829c8c broke the Svelte language tools - presumably having paths outside of the repo is confusing them. As a plan B, the symlinks have been shifted to a single subdir. Along with some exclusions in the VS Code config, this should allow VS Code to continue to work out of the box, but the docs will need updating to reflect the extra work required for PyCharm/IntelliJ. + fix svelte-check execution on a system without node installed. It still throws up some errors that are presumably caused by our multiple rootDirs - not sure if there's an easy way to work around that.
2022-01-24 02:06:02 +01:00
"files.watcherExclude": {
"**/.git/objects/**": true,
"**/.git/subtree-cache/**": true,
"**/node_modules/*/**": true,
disable automatic mypy invocation in VS Code The default settings don't understand our folder layout (leading to errors), and place cache files in the root folder. While there is a setting to provide extra arguments to mypy which we could use to address the former, paths like ~/.cache do not appear to be supported. Easier to just rely on pyright for in-IDE linting, and invoke mypy either via bazel, or via tools/mypy-watch + remove unused dist/ exclude
2022-02-17 04:25:22 +01:00
".bazel/**": true
switch convenience symlinks to .bazel/ Unfortunately 5efaf5a4be95e289210e964a5cd40b4f08829c8c broke the Svelte language tools - presumably having paths outside of the repo is confusing them. As a plan B, the symlinks have been shifted to a single subdir. Along with some exclusions in the VS Code config, this should allow VS Code to continue to work out of the box, but the docs will need updating to reflect the extra work required for PyCharm/IntelliJ. + fix svelte-check execution on a system without node installed. It still throws up some errors that are presumably caused by our multiple rootDirs - not sure if there's an easy way to work around that.
2022-01-24 02:06:02 +01:00
},
add some more VS Code workspace settings for Python/Rust
2022-01-23 07:39:40 +01:00
"python.analysis.extraPaths": ["./pylib"],
"python.formatting.provider": "black",
disable automatic mypy invocation in VS Code The default settings don't understand our folder layout (leading to errors), and place cache files in the root folder. While there is a setting to provide extra arguments to mypy which we could use to address the former, paths like ~/.cache do not appear to be supported. Easier to just rely on pyright for in-IDE linting, and invoke mypy either via bazel, or via tools/mypy-watch + remove unused dist/ exclude
2022-02-17 04:25:22 +01:00
"python.linting.mypyEnabled": false,
add some more VS Code workspace settings for Python/Rust
2022-01-23 07:39:40 +01:00
"rust-analyzer.cargo.runBuildScripts": true,
"rust-analyzer.checkOnSave.allTargets": false,
disable automatic mypy invocation in VS Code The default settings don't understand our folder layout (leading to errors), and place cache files in the root folder. While there is a setting to provide extra arguments to mypy which we could use to address the former, paths like ~/.cache do not appear to be supported. Easier to just rely on pyright for in-IDE linting, and invoke mypy either via bazel, or via tools/mypy-watch + remove unused dist/ exclude
2022-02-17 04:25:22 +01:00
"rust-analyzer.files.excludeDirs": [".bazel", "node_modules"],
add some more VS Code workspace settings for Python/Rust
2022-01-23 07:39:40 +01:00
"rust-analyzer.procMacro.enable": true,
// this formats 'use' blocks in a nicer way, but requires you to run
// 'rustup install nightly'.
switch convenience symlinks to .bazel/ Unfortunately 5efaf5a4be95e289210e964a5cd40b4f08829c8c broke the Svelte language tools - presumably having paths outside of the repo is confusing them. As a plan B, the symlinks have been shifted to a single subdir. Along with some exclusions in the VS Code config, this should allow VS Code to continue to work out of the box, but the docs will need updating to reflect the extra work required for PyCharm/IntelliJ. + fix svelte-check execution on a system without node installed. It still throws up some errors that are presumably caused by our multiple rootDirs - not sure if there's an easy way to work around that.
2022-01-24 02:06:02 +01:00
"rust-analyzer.rustfmt.extraArgs": ["+nightly"],
"search.exclude": {
"**/node_modules": true,
disable automatic mypy invocation in VS Code The default settings don't understand our folder layout (leading to errors), and place cache files in the root folder. While there is a setting to provide extra arguments to mypy which we could use to address the former, paths like ~/.cache do not appear to be supported. Easier to just rely on pyright for in-IDE linting, and invoke mypy either via bazel, or via tools/mypy-watch + remove unused dist/ exclude
2022-02-17 04:25:22 +01:00
".bazel/**": true
switch convenience symlinks to .bazel/ Unfortunately 5efaf5a4be95e289210e964a5cd40b4f08829c8c broke the Svelte language tools - presumably having paths outside of the repo is confusing them. As a plan B, the symlinks have been shifted to a single subdir. Along with some exclusions in the VS Code config, this should allow VS Code to continue to work out of the box, but the docs will need updating to reflect the extra work required for PyCharm/IntelliJ. + fix svelte-check execution on a system without node installed. It still throws up some errors that are presumably caused by our multiple rootDirs - not sure if there's an easy way to work around that.
2022-01-24 02:06:02 +01:00
}
add some more VS Code workspace settings for Python/Rust
2022-01-23 07:39:40 +01:00
}
Reference in New Issue Copy Permalink