-
I use |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Hey 👋 Which settings do you need to configure on a per-project basis? Neoconf requires a I'll create a feature request for now (#53), and look into it when I have some more time. |
Beta Was this translation helpful? Give feedback.
-
Here's the example coming from the project RISC-V based system kernel. // .neoconf.json
{
"lspconfig": {
"rust_analyzer": {
"rust-analyzer.checkOnSave.command": "clippy",
"rust-analyzer.checkOnSave.allTargets": false,
"rust-analyzer.cargo.target": "riscv64gc-unknown-none-elf"
}
}
} |
Beta Was this translation helpful? Give feedback.
-
To inform anyone reading the solution when you migrate the setting from neoconf, you can copy and paste the content in // .neoconf.json
{
- "lspconfig": {
- "rust_analyzer": {
"rust-analyzer.checkOnSave.command": "clippy",
"rust-analyzer.checkOnSave.allTargets": false,
"rust-analyzer.cargo.target": "riscv64gc-unknown-none-elf"
- }
- }
} to obtain: // rust-analyzer.json under project root
{
"rust-analyzer.checkOnSave.command": "clippy",
"rust-analyzer.checkOnSave.allTargets": false,
"rust-analyzer.cargo.target": "riscv64gc-unknown-none-elf"
} then use |
Beta Was this translation helpful? Give feedback.
Those are rust-analyzer settings, so it can be solved with #51 (which I've just implemented and released).
See the section in the readme for details.
The JSON would have to look like this:
If you want to reuse your neoconf settings, you can use this function as a reference to load them.
I do plan to add support for neoconf, but unfortunately I don't have time for that right now (probably not before December).