990d2330db
Intends to clarify how to make Embassy usable from within Visual Studio Code by assuming the presence of the Rust Analyzer. Note that IntelliJ does not support the Rust Analyzer, so an open question remains as to the whether this is a good move. If it turns out not to be a good move then we should still look at clarifying the use of a workspace file.
30 lines
No EOL
1.1 KiB
JSON
30 lines
No EOL
1.1 KiB
JSON
{
|
|
"editor.formatOnSave": true,
|
|
"rust-analyzer.assist.importEnforceGranularity": true,
|
|
"rust-analyzer.assist.importGranularity": "module",
|
|
"rust-analyzer.checkOnSave.allFeatures": false,
|
|
"rust-analyzer.checkOnSave.allTargets": false,
|
|
"rust-analyzer.checkOnSave.command": "clippy",
|
|
"rust-analyzer.cargo.noDefaultFeatures": true,
|
|
"rust-analyzer.experimental.procAttrMacros": false,
|
|
"rust-analyzer.checkOnSave.noDefaultFeatures": true,
|
|
"rust-analyzer.cargo.target": "thumbv7em-none-eabi",
|
|
"rust-analyzer.cargo.features": [
|
|
// These are needed to prevent embassy-net from failing to build
|
|
//"embassy-net/medium-ethernet",
|
|
//"embassy-net/tcp",
|
|
//"embassy-net/pool-16",
|
|
],
|
|
"rust-analyzer.linkedProjects": [
|
|
// Declare for the target you wish to develop
|
|
"examples/nrf/Cargo.toml"
|
|
],
|
|
"rust-analyzer.procMacro.enable": true,
|
|
"rust-analyzer.cargo.runBuildScripts": true,
|
|
"files.watcherExclude": {
|
|
"**/.git/objects/**": true,
|
|
"**/.git/subtree-cache/**": true,
|
|
"**/target/**": true
|
|
},
|
|
"git.ignoreLimitWarning": true
|
|
} |