aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package.json
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Start LSP 3.17 supportJeremy Kolb2021-02-141-3/+3
|
* Allow automatically detect the rustc-src directory (fixes #3517).Benjamin Bouvier2021-02-131-1/+1
| | | | | If the configured rustcSource is set to "discover", try to automatically detect a source from the sysroot rustc directory.
* Add **Copy Run Command Line** command for vscodeAleksey Kladov2021-02-101-0/+5
| | | | | This is useful when you want to, e.g., run a specific test in a terminal with `--release`.
* Fix highlighting of injected attributesAleksey Kladov2021-02-091-0/+44
|
* Add config option to ignore directoriesAleksey Kladov2021-01-261-0/+8
|
* Remove the need to manually sync config in package.jsonAleksey Kladov2021-01-261-5/+7
|
* Add References code lens.vsrs2021-01-231-0/+5
| | | | For Struct, Enum, Union and Trait symbols.
* Use american spelling for configAleksey Kladov2021-01-071-1/+1
| | | | | | | | As per https://github.com/rust-analyzer/rust-analyzer/blob/171c3c08fe245938fb25321394233de5fe2abc7c/docs/dev/style.md#variable-naming Also implement config aliasing, for pain-free settings migrations in the future
* More maintainable configAleksey Kladov2021-01-061-0/+8
| | | | | | | Rather than eagerly converting JSON, we losslessly keep it as is, and change the shape of user-submitted data at the last moment. This also allows us to remove a bunch of wrong Defaults
* Rename extension configAleksey Kladov2021-01-041-1/+1
|
* Merge #7068bors[bot]2021-01-031-0/+9
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7068: Add VSCode command to view the hir of a function body r=theotherphil a=theotherphil Will fix https://github.com/rust-analyzer/rust-analyzer/issues/7061. Very rough initial version just to work out where I needed to wire everything up. @matklad would you be happy merging a hir visualiser of some kind? If so, do you have any thoughts on what you'd like it show, and how? I've spent very little time on this thus far, so I'm fine with throwing away the contents of this PR, but I want to avoid taking the time to make this more polished/interactive/useful only to discover that no-one else has any interest in this functionality. ![image](https://user-images.githubusercontent.com/1974256/103236081-bb58f700-493b-11eb-9d12-55ae1b870f8f.png) Co-authored-by: Phil Ellison <[email protected]>
| * Initial implementation of view-hir commandPhil Ellison2020-12-281-0/+9
| |
* | Add an option for extra env vars in the Code extensionlf-2020-12-301-0/+8
|/
* Merge #6993bors[bot]2020-12-221-25/+25
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6993: Clean up descriptions for settings r=matklad a=rherrmann Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, command line arguments, etc. as `code`. Format mentions of UI elements in _italic_. Fix typos, add missing full-stops, add missing default values. Co-authored-by: Rüdiger Herrmann <[email protected]>
| * Clean up descriptions for settingsRüdiger Herrmann2020-12-221-25/+25
| | | | | | | | | | | | | | | | | | | | | | | | Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
* | Remove TextMate grammarLaurențiu Nicola2020-12-211-5/+0
|/ | | | It's now included upstream in VS Code
* LSP 3.16 - Releasedkjeremy2020-12-171-3/+3
|
* add a language configuration for VS CodeDusty Pomerleau2020-12-131-0/+11
|
* Make config.rs a single source of truth for configuration.Aleksey Kladov2020-12-081-320/+304
| | | | | | | | | | | | | | | | | Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
* Better config nameKirill Bulatov2020-12-081-3/+6
|
* Disable the completion for no corresponding client resolve capabilitiesKirill Bulatov2020-12-071-3/+3
|
* Update npm packageskjeremy2020-12-071-14/+14
|
* Merge #6496bors[bot]2020-11-261-3/+0
|\ | | | | | | | | | | | | | | | | | | 6496: Use builtin scopes more r=matklad a=georgewfraser VSCode has added more builtin fallback scopes, so we can remove some of our fallback scopes by aligning with their conventions. Note that the macro scope doesn't seem to actually *work* at the moment. I have filed a bug with VSCode: https://github.com/microsoft/vscode/issues/110150 Co-authored-by: George Fraser <[email protected]>
| * Just remove the macro fallbackGeorge Fraser2020-11-251-0/+6
| |
| * Use builtin scopes moreGeorge Fraser2020-11-071-9/+0
| |
* | Gate autoimports begind experimental completions flagKirill Bulatov2020-11-241-0/+5
| |
* | Use vscode-languageclient 7.0.0-next.14kjeremy2020-11-171-2/+2
| |
* | Cleanup workspace loading a tiny bitAleksey Kladov2020-11-131-5/+5
| |