aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package.json
Commit message (Collapse)AuthorAgeFilesLines
* Allow to disable import insertion on single path glob importsLukas Wirth2021-06-181-0/+5
|
* Merge #9258bors[bot]2021-06-161-4/+4
|\ | | | | | | | | | | | | | | 9258: minor: Give `ImportPrefix` variants better config names r=matklad a=Veykril I feel like `crate` and `self` work better than `by_crate` and `by_self`. The only reason for the current names were that `Self` doesn't work for the variant name on the rust side so I forgot about setting proper config names on serde layer. Co-authored-by: Lukas Wirth <[email protected]>
| * Give ImportPrefix variants better config namesLukas Wirth2021-06-131-4/+4
| |
| |
| \
*-. | Merge #9267 #9279bors[bot]2021-06-151-1/+1
|\ \| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 9267: fix: Code: update the LSP server without asking r=matklad a=lnicola Most LSP extensions seem to do the same thing, and this is causing some confusion for users who don't notice the update prompt before Code hides it. 9279: minor: Document installation via Homebrew r=matklad a=Svetlitski `rust-analyzer` can be installed via [Homebrew](https://brew.sh) (AKA`brew`) on macOS. I've added instructions on how to do so to the documentation. Additionally, I added a `.gitignore` rule to ignore the HTML documentation produced by `asciidoctor manual.adoc` so that it is not accidentally checked into `git`. Co-authored-by: Laurențiu Nicola <[email protected]> Co-authored-by: Kevin Svetlitski <[email protected]> Co-authored-by: Aleksey Kladov <[email protected]>
| * | Code: automatically update the LSP serverLaurențiu Nicola2021-06-141-1/+1
| |/ | | | | | | | | | | Most LSP extensions seem to do the same thing, and this is causing some confusion for users who don't notice the update prompt before Code hides it.
* / Use objects instead of bools for markers in package.jsonLaurențiu Nicola2021-06-151-2/+2
|/
* Add function references hover actionLukas Wirth2021-06-041-0/+5
|
* Make it opt-inJonas Schievink2021-06-031-0/+5
|
* Document that `addCallArgumentSnippets` requires `addCallParenthesisLukas Wirth2021-06-021-1/+1
|
* Add config setting for self-on-the-flyLukas Wirth2021-05-311-0/+5
|
* Fix incorrect setting descriptionsLucas Schwiderski2021-05-291-2/+2
| | | | | | | | Descriptions for diagnostic warning hint and info display were swapped. Fixes #8485. Signed-off-by: Lucas Schwiderski <[email protected]>
* implement range formattingAndy Russell2021-05-231-0/+5
|
* Add a "Debug ItemTree" LSP requestJonas Schievink2021-05-211-0/+5
|
* Merge #8873bors[bot]2021-05-201-7/+14
|\ | | | | | | | | | | | | | | | | | | | | | | 8873: Implement import-granularity guessing r=matklad a=Veykril This renames our `MergeBehavior` to `ImportGranularity` as rustfmt has it as the purpose of them are basically the same. `ImportGranularity::Preserve` currently has no specific purpose for us as we don't have an organize imports assist yet, so it currently acts the same as `ImportGranularity::Item`. We now try to guess the import style on a per file basis and fall back to the user granularity setting if the file has no specific style yet or where it is ambiguous. This can be turned off by setting `import.enforceGranularity` to `true`. Closes https://github.com/rust-analyzer/rust-analyzer/issues/8870 Co-authored-by: Lukas Tobias Wirth <[email protected]>
| * Replace ImportGranularity::Guess with guessing boolean flagLukas Tobias Wirth2021-05-191-3/+6
| |
| * Add ImportGranularity::GuessLukas Tobias Wirth2021-05-181-1/+3
| |
| * MergeBehavior -> ImportGranularityLukas Tobias Wirth2021-05-181-8/+10
| |
* | Add new LSP extension for workspace symbol lookupalcroito2021-05-171-0/+26
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new extension allows filtering of workspace symbool lookup results by search scope or search kind. Filtering can be configured in 3 different ways: - The '#' or '*' markers can be added inline with the symbol lookup query. The '#' marker means symbols should be looked up in the current workspace and any dependencies. If not specified, only current workspace is considered. The '*' marker means all kinds of symbols should be looked up (types, functions, etc). If not specified, only type symbols are returned. - Each LSP request can take an optional search_scope or search_kind argument query parameter. - Finally there are 2 global config options that can be set for all requests served by the active RA instance. Add support for setting the global config options to the VSCode extension. The extension does not use the per-request way, but it's useful for other IDEs. The latest version of VSCode filters out the inline markers, so currently the only reasonable way to use the new functionality is via the global config.
* minor: adjust config nameAleksey Kladov2021-05-171-5/+5
|
* Merge #8795bors[bot]2021-05-171-0/+5
|\ | | | | | | | | | | | | | | | | | | 8795: Allow semantic tokens for strings to be disabled r=matklad a=djrenren Fixes https://github.com/rust-analyzer/rust-analyzer/issues/7111 Pretty straightforward change, but open to any suggestions if there's a more recommended testing strategy than what I went with. Co-authored-by: John Renner <[email protected]>
| * Formatting and docsJohn Renner2021-05-101-0/+5
| |
* | Allow viewing the crate graph in a webviewJonas Schievink2021-05-111-0/+5
| |
* | Give MergeBehaviour variants better namesLukas Wirth2021-05-101-6/+6
| |
* | :arrow_up: package-lock.jsonAleksey Kladov2021-05-081-1/+4
|/
* internal: ensure that client and server-side configs are not mixed upAleksey Kladov2021-04-281-6/+6
| | | | https://github.com/rust-lang/rust/issues/84647 would help big time here.
* Merge #8624bors[bot]2021-04-271-2/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8624: Automatically detect rust library source file map r=vsrs a=vsrs This PR adds a new possible `rust-analyzer.debug.sourceFileMap` value: ```json { "rust-analyzer.debug.sourceFileMap": "auto" } ``` I did not make it the default because it uses two shell calls (`rustc --print sysroot` and `rustc -V -v`). First one can be slow (https://github.com/rust-lang/rustup/issues/783) Fixes #8619 Co-authored-by: vsrs <[email protected]>
| * Add special `auto` value for `debug.sourceFileMap`vsrs2021-04-221-2/+3
| |
* | add option to package.jsonJorge Mederos Alvarado2021-04-271-0/+5
|/
* Code review feedback.James Leitch2021-04-211-2/+2
|
* Diagnostic Remap Path Prefixes added.James Leitch2021-04-211-1/+6
|
* feat: avoid checking the whole project during initial loadingAleksey Kladov2021-04-121-0/+5
|
* Bump the default hint lengthKirill Bulatov2021-03-231-1/+1
|
* Limit the hints size by defaultKirill Bulatov2021-03-231-2/+2
|
* Item up and down moversivan7702021-03-181-0/+10
|
* Enable proc-macros by defaultAleksey Kladov2021-03-151-1/+1
|
* Merge #7799bors[bot]2021-03-131-1/+13
|\ | | | | | | | | | | | | | | | | | | | | | | | | 7799: Related tests r=matklad a=vsrs ![tests](https://user-images.githubusercontent.com/62505555/109397453-a9013680-7947-11eb-8b11-ac03079f7645.gif) This adds an ability to look for tests for the item under the cursor: function, constant, data type, etc The LSP part is bound to change. But the feature itself already works and I'm looking for a feedback :) Co-authored-by: vsrs <[email protected]>
| * Add progress reportingvsrs2021-02-271-1/+8
| |
| * Add LSP request and VSCode commandvsrs2021-02-271-0/+5
| |
* | Make code less surprisingAleksey Kladov2021-03-091-24/+24
| | | | | | | | Theres no reason to have literal `\n\n` in the source code
* | Add more documentation for rustc_privateJoshua Nelson2021-03-081-1/+1
| |
* | Merge #7891bors[bot]2021-03-081-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7891: Improve handling of rustc_private r=matklad a=DJMcNab This PR changes how `rust-analyzer` handles `rustc_private`. In particular, packages now must opt-in to using `rustc_private` in `Cargo.toml`, by adding: ```toml [package.metadata.rust-analyzer] rustc_private=true ``` This means that depending on crates which also use `rustc_private` will be significantly improved, since their dependencies on the `rustc_private` crates will be resolved properly. A similar approach could be used in #6714 to allow annotating that your package uses the `test` crate, although I have not yet handled that in this PR. Additionally, we now only index the crates which are transitive dependencies of `rustc_driver` in the `rustcSource` directory. This should not cause any change in behaviour when using `rustcSource: "discover"`, as the source used then will only be a partial clone. However, if `rustcSource` pointing at a local checkout of rustc, this should significantly improve the memory usage and lower indexing time. This is because we avoids indexing all crates in `src/tools/`, which includes `rust-analyzer` itself. Furthermore, we also prefer named dependencies over dependencies from `rustcSource`. This ensures that feature resolution for crates which are depended on by both `rustc` and your crate uses the correct set for analysing your crate. See also [introductory zulip stream](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Fixed.20crate.20graphs.20and.20optional.20builtin.20crates/near/229086673) I have tested this in [priroda](https://github.com/oli-obk/priroda/), and it provides a significant improvement to the development experience (once I give `miri` the required data in `Cargo.toml`) Todo: - [ ] Documentation This is ready to review, and I will add documentation if this would be accepted (or if I get time to do so anyway) Co-authored-by: Daniel McNab <[email protected]>
| * | Document rustc_private in metadataDaniel McNab2021-03-081-1/+1
| | |
| * | Revert "Support disabling rustc build scripts"Daniel McNab2021-03-081-5/+0
| | | | | | | | | | | | This reverts commit ddce6bb282764692d53b719bff4c37e3512d4556.
| * | Support disabling rustc build scriptsDaniel McNab2021-03-081-0/+5
| | |
* | | Make code completion "just work" in more casesAleksey Kladov2021-03-081-1/+1
| | |
* | | Merge #7901bors[bot]2021-03-081-0/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7901: Make extension respect http proxy settings r=matklad a=kamyuentse This patch makes vscode extension respect proxy settings when fetching release metadata and rust-analyzer binary. Co-authored-by: Kam Y. Tse <[email protected]>
| * | | Make extension respect http proxy settingsKam Y. Tse2021-03-071-0/+1
| |/ /
* / / Make group imports configurableasv2021-03-071-0/+5
|/ /
* / Migrate to user-centric config name for `cargo check` stuffAleksey Kladov2021-03-041-3/+3
|/
* Update our vscode npm packageskjeremy2021-02-231-3/+3
|