about summary refs log tree commit diff
path: root/editors/code/src
AgeCommit message (Collapse)AuthorLines
2023-05-02fixing TS linting, removing importBruno Ortiz-1/+0
2023-05-02Accepting review suggestionsBruno Ortiz-6/+19
2023-05-02fixing ts linting and rust testBruno Ortiz-14/+15
2023-05-02final rabasing fixesBruno Ortiz-104/+23
2023-05-02accepting review suggestionsBruno Ortiz-3/+3
2023-05-02reveal only when tree is visibleBruno Ortiz-12/+29
2023-05-02Adding crate_root_path to crate_graphBruno Ortiz-2/+6
2023-05-02improving code to work with multi-workspacesBruno Ortiz-18/+84
2023-05-02Fixing naming from graph to listBruno Ortiz-11/+9
2023-05-02running prettierBruno Ortiz-91/+86
2023-05-02removing unused codeBruno Ortiz-13/+6
2023-05-02WIP: Add lsp-ext scaffoldLukas Wirth-3/+23
2023-05-02Reformat VSCode client codeLukas Wirth-41/+36
2023-05-02removing unused functionbruno-ortiz-26/+0
2023-05-02fixing linting problemasbruno-ortiz-30/+36
2023-05-02fixing stblib loadingbruno-ortiz-1/+2
2023-05-02Creating rust dependencies tree viewbruno-ortiz-5/+106
2023-05-02fetching dependencies from the serverBruno Ortiz-152/+56
2023-05-02WIP: Add lsp-ext scaffoldLukas Wirth-1/+24
2023-05-02Remove unnecessary openFile commandLukas Wirth-12/+1
2023-05-02Reformat VSCode client codeLukas Wirth-72/+82
2023-05-02removing unused functionbruno-ortiz-26/+0
2023-05-02fixing linting problemasbruno-ortiz-131/+131
2023-05-02fixing stblib loadingbruno-ortiz-1/+4
2023-05-02Creating rust dependencies tree viewbruno-ortiz-69/+393
2023-05-02Highlight closure captures when cursor is on pipeLukas Wirth-6/+3
2023-05-01MIR episode 4hkalbasi-6/+34
2023-04-28fix: Fix restart server button trying to start instead of restart the serverLukas Wirth-7/+6
2023-04-20using VSCode's native parameterHints.enabled settingNagy Botond-4/+4
2023-04-20Automatic parameter hints trigger can be toggled on/offNagy Botond-1/+7
2023-04-19SpellingJosh Soref-1/+1
* a rule * access * after * amount * annotations * assignment * assist * associated * attribute * borrowed * built-in type * clarification * command * const * constructor * corresponding * counterparts * curlies * dependencies * deterministic * diagnostic * duplicates * edge * edited * efficient * elsewhere * execution * expression * extensions * extracted * fill * github * helper * heuristic * incomplete * indent end * inlay * invocation * lifetime * looking * maybe * move * mutability * mutable * necessarily * necessary * negative * nonexistent * occurred * offsets * offsetted * overridden * parameters * params * params_and_where_preds_in_scope * paredit * parent * parentheses * prepended if * punctuation * receive * receiver * referring * repeated * representing * semantically * separately * shouldnot * siblings * similar * something's * statement * struct * structure * surprise * the * this * transparent * unimplemented * unnamed * unnecessary * unneeded * unreachable * unterminated * utilities * variant * variants * visibility * work around (v) * workaround Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
2023-04-13minor: Allow copying the graphviz source from the view crategraph webviewLukas Wirth-1/+6
2023-04-13fix: Fix view crate graph being broken due to webworker usageLukas Wirth-2/+2
2023-04-10fix: when running the "discoverProjectCommand", use the Rust file'sDavid Barsky-12/+15
parent directory instead of the workspace folder.
2023-04-09fix: Fix project linking popup appearing for modules that can be linked to a ↵Lukas Wirth-1/+5
crate
2023-04-04fix: Fix relative path creation using the wrong path accessorLukas Wirth-5/+9
2023-04-04fix: Fix vscode project linking popup buttons being swappedLukas Wirth-3/+4
2023-04-02Don't append "!" to non-bang macro nameRyo Yoshida-1/+1
2023-03-30Missing runnable env on debug targetRungsikorn Rungsikavarnich-4/+12
Fix bug in Rust Analyzer where runnable debugging did not pass environment variable from configuration to child process of Cargo on binary build stage
2023-03-28Auto merge of #14366 - Veykril:linked-proj, r=Veykrilbors-12/+64
feat: Pop a notification prompting the user to add a Cargo.toml of unlinked file to the linkedProjects cc https://github.com/rust-lang/rust-analyzer/issues/13226 https://github.com/rust-lang/rust-analyzer/issues/9661
2023-03-26finish renaming `rust-analyzer/reloadProcMacros` to ↵David Barsky-1/+1
`rust-analyzer/rebuildProcMacros`
2023-03-26Handle proc macro fetching via OpQueueLukas Wirth-5/+5
2023-03-25Add lsp command for rebuilding proc macrosLukas Wirth-1/+10
2023-03-25Fix lintsLukas Wirth-42/+37
2023-03-21Fix VS Code status message formatting errorx2cf-1/+1
2023-03-16feat: Pop a notification prompting the user to add a Cargo.toml of unlinked ↵Lukas Wirth-11/+68
file to the linkedProjects
2023-03-14Auto merge of #14307 - ↵bors-11/+231
davidbarsky:davidbarsky/add-cargo-style-project-discovery-for-buck-and-bazel-sickos, r=Veykril Add Cargo-style project discovery for Buck and Bazel Users This feature requires the user to add a command that generates a `rust-project.json` from a set of files. Project discovery can be invoked in two ways: 1. At extension activation time, which includes the generated `rust-project.json` as part of the linkedProjects argument in `InitializeParams`. 2. Through a new command titled "rust-analyzer: Add current file to workspace", which makes use of a new, rust-analyzer-specific LSP request that adds the workspace without erasing any existing workspaces. Note that there is no mechanism to _remove_ workspaces other than "quit the rust-analyzer server". Few notes: - I think that the command-running functionality _could_ merit being placed into its own extension (and expose it via extension contribution points) to provide build-system idiomatic progress reporting and status handling, but I haven't (yet) made an extension that does this nor does Buck expose this sort of functionality. - This approach would _just work_ for Bazel. I'll try and get the tool that's responsible for Buck integration open-sourced soon. - On the testing side of things, I've used this in around my employer's Buck-powered monorepo and it's a nice experience. That being said, I can't think of an open-source repository where this can be tested in public, so you might need to trust me on this one. I'd love to get feedback on: - Naming of LSP extensions/new commands. I'm not too pleased with how "rust-analyzer: Add current file to workspace" is named, in that it's creating a _new_ workspace. I think that this command being added should be gated on `rust-analyzer.discoverProjectCommand` on being set, so I can add this in sequent commits. - My Typescript. It's not particularly good. - Suggestions on handling folders with _both_ Cargo and non-Cargo build systems and if I make activation a bit better. (I previously tried to add this functionality entirely within rust-analyzer-the-LSP server itself, but matklad was right—an extension side approach is much, much easier.)
2023-03-14fix: don't override `linkedProjects` if no workspace was discovered.David Barsky-2/+9
2023-03-14Address review commentsDavid Barsky-1/+11
2023-03-13Remove `rust-analyzer/addProject` in favor of notifying r-a that ↵David Barsky-6/+1
configuration has changed
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-16 02:43:40 +0000