aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | Merge #5207bors[bot]2020-07-031-17/+4
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5207: :arrow_up: salsa r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | :arrow_up: salsaAleksey Kladov2020-07-031-17/+4
|/ / /
* | | Merge #5205bors[bot]2020-07-031-795/+178
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5205: Refactor attribut completion tests r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Refactor attribut completion testsAleksey Kladov2020-07-031-645/+115
| | | |
| * | | Compress attribute completion testsAleksey Kladov2020-07-031-150/+63
| | | |
* | | | Merge #5202bors[bot]2020-07-036-25/+235
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5202: Runnable env r=matklad a=vsrs This PR adds on option to specify (in the settings.json) environment variables passed to the runnable. The simplest way for all runnables in a bunch: ```jsonc "rust-analyzer.runnableEnv": { "RUN_SLOW_TESTS": "1" } ``` Or it is possible to specify vars more granularly: ```jsonc "rust-analyzer.runnableEnv": [ { // "mask": null, // null mask means that this rule will be applied for all runnables env: { "APP_ID": "1", "APP_DATA": "asdf" } }, { "mask": "test_name", "env": { "APP_ID": "2", // overwrites only APP_ID } } ] ``` You can use any valid RegExp as a mask. Also note that a full runnable name is something like *run bin_or_example_name*, *test some::mod::test_name* or *test-mod some::mod*, so it is possible to distinguish binaries, single tests, and test modules with this masks: `"^run"`, `"^test "` (the trailing space matters!), and `"^test-mod"` respectively. Fixes #4450 I suppose this info should be somewhere in the docs, but unsure where is the best place. Co-authored-by: vsrs <[email protected]>
| * | | Fix tag levelvsrs2020-07-031-1/+1
| | | |
| * | | remove ---vsrs2020-07-031-6/+4
| | | |
| * | | Add docsvsrs2020-07-031-12/+46
| | | |
| * | | Fix workspaceRootvsrs2020-07-031-1/+3
| | | |
| * | | code lintingvsrs2020-07-033-32/+32
| | | |
| * | | Add testsvsrs2020-07-034-10/+128
| | | |
| * | | Add runnable env support.vsrs2020-07-034-11/+69
| | | |
* | | | Merge #5116bors[bot]2020-07-0343-442/+593
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5116: Categorize assists r=matklad a=kjeremy Categorize assists so that editors can use them. Follows the LSP spec pretty close (and some things may need adjustments) but this populates the Refactor menu in vscode and pushes quickfixes through again. This is a prerequisite to filtering out assists that the client doesn't care about. Fixes #4147 Co-authored-by: Jeremy Kolb <[email protected]> Co-authored-by: kjeremy <[email protected]>
| * | | Don't categorize things we don't care aboutkjeremy2020-07-026-68/+52
| | | |
| * | | Move AssistKind into AssistIdkjeremy2020-07-0241-140/+90
| | | |
| * | | Recategorize a fewkjeremy2020-07-023-3/+3
| | | |
| * | | Pass CodeActionKind through our middleware to populate menusJeremy Kolb2020-07-021-2/+4
| | | |
| * | | Categorize assistsJeremy Kolb2020-07-0242-506/+721
| | | |
* | | | Merge #5201bors[bot]2020-07-032-1/+22
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5201: Add function to test completion edit r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Add function to test completion editAleksey Kladov2020-07-032-1/+22
|/ / /
* | | Merge #5200bors[bot]2020-07-031-206/+198
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5200: Refactor keyword completion tests r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Refactor keyword completion testsAleksey Kladov2020-07-031-206/+198
|/ / /
* | | Merge #5199bors[bot]2020-07-034-374/+227
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | 5199: Cleanup record completion tests r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Cleanup record completion testsAleksey Kladov2020-07-034-374/+227
|/ /
* | Merge #5192bors[bot]2020-07-022-8/+17
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 5192: Implement rust-analyzer feature configuration to tests. r=matklad a=daxpedda Fixes #3198. I'm unsure if it is desired this way, maybe we want to make a seperate configuration? Co-authored-by: daxpedda <[email protected]>
| * | Implement rust-analyzer feature configuration to tests.daxpedda2020-07-022-8/+17
| |/
* | Merge #5193bors[bot]2020-07-024-43/+56
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5193: Move cargo metadata off the main loop r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Move cargo metadata off the main loopAleksey Kladov2020-07-024-43/+56
|/ /
* | Merge #5191bors[bot]2020-07-022-22/+9
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5191: Minor r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | MinorAleksey Kladov2020-07-022-22/+9
| |/
* | Merge #5188bors[bot]2020-07-0210-12/+144
|\ \ | | | | | | | | | | | | | | | | | | | | | 5188: Implement StatusBar r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | Indicate when project needs a reloadAleksey Kladov2020-07-024-7/+51
| | |
| * | Implement StatusBarAleksey Kladov2020-07-028-5/+93
| | |
* | | Merge #5189bors[bot]2020-07-022-9/+207
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | 5189: Record and suggest assoc. items of traits via ImportMap r=matklad a=jonas-schievink Fixes https://github.com/rust-analyzer/rust-analyzer/issues/5115 Co-authored-by: Jonas Schievink <[email protected]>
| * | Use SmolStrJonas Schievink2020-07-021-3/+4
| | |
| * | Fix testsJonas Schievink2020-07-021-1/+27
| | |
| * | Record and suggest trait items via ImportMapJonas Schievink2020-07-022-8/+179
| | |
| | |
| \ \
| \ \
| \ \
| \ \
| \ \
| \ \
| \ \
*-------. \ \ Merge #5089 #5161 #5184 #5185 #5186bors[bot]2020-07-0210-26/+242
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5089: Disable auto-complete on comments r=matklad a=BGluth Resolves #4907 by disabling any auto-completion on comments. As flodiebold [pointed out](https://github.com/rust-analyzer/rust-analyzer/issues/4907#issuecomment-648439979), in the future we may want to support some form of auto-completion within doc comments, but for now it was suggested to just disable auto-completion on them entirely. The implementation involves adding a new field `is_comment` to `CompletionContext` and checking if the immediate token we auto-completed on is a comment. I couldn't see a case where we need to check any of the ancestors, but let me know if this is not sufficient. I also wasn't sure if it was necessary to add a new field to this struct, but I decided it's probably the best option if we want to potentially do auto-completion on doc comments in the future. Finally, the three tests I added should I think ideally not filter results by `CompletionKind::Keyword`, but if I want to get unfiltered results, I need access to a non-public function [get_all_completion_items](https://github.com/rust-analyzer/rust-analyzer/blob/9a4d02faf9c47f401b8756c3f7fcab2198f5f9cd/crates/ra_ide/src/completion/test_utils.rs#L32-L39) which I don't know if I should make public just for this. 5161: SSR: Add initial support for placeholder constraints r=matklad a=davidlattimore 5184: Always install required nightly extension if current one is not nightly r=matklad a=Veetaha This is weird, but having switched back to stable by uninstalling the extension appears that vscode doesn't destroy the `PersistentState` and thus changing to `nightly` channel doesn't work because the last check for nightly extension was less than 1 hour ago. The simple solution is to skip this check if we know that the current extension version is not nightly. 5185: Force showing extension activation error pop-up notification r=matklad a=Veetaha Fixes https://github.com/rust-analyzer/rust-analyzer/issues/5091 5186: fix: correct pd/ppd/tfn/tmod completion doc r=matklad a=fannheyward https://github.com/rust-analyzer/rust-analyzer/blob/a33eefa3b26000b3018e6bb873f18dbe15ab4ab7/crates/ra_ide/src/completion/complete_snippet.rs#L23-L24 Co-authored-by: BGluth <[email protected]> Co-authored-by: David Lattimore <[email protected]> Co-authored-by: Veetaha <[email protected]> Co-authored-by: Heyward Fann <[email protected]>
| | | | | * | | fix: correct pd/ppd/tfn/tmod completion docHeyward Fann2020-07-021-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://github.com/rust-analyzer/rust-analyzer/blob/a33eefa3b26000b3018e6bb873f18dbe15ab4ab7/crates/ra_ide/src/completion/complete_snippet.rs#L23
| | | | * | | | Force showing extension activation error pop-up notificationVeetaha2020-07-021-3/+11
| | | | | | | |
| | | * | | | | Always install required nightly extension if current one is not nightlyVeetaha2020-07-021-4/+8
| | | |/ / / /
| | * | | | | SSR: Use T! instead of SyntaxKind::* where possibleDavid Lattimore2020-07-021-11/+11
| | | | | | |
| | * | | | | SSR: Add initial support for placeholder constraintsDavid Lattimore2020-07-016-6/+156
| | | | | | |
| * | | | | | Auto-completion no longer occurs on commentsBGluth2020-07-011-1/+5
| | | | | | |
| * | | | | | Added tests for no auto-completion on commentsBGluth2020-07-011-0/+50
| | |_|/ / / | |/| | | |
* | | | | | Merge #5180bors[bot]2020-07-021-0/+2
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5180: Disable optimizations for tracing-attributes r=matklad a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | | | | Disable optimizations for tracing-attributesLaurențiu Nicola2020-07-011-0/+2
| | |_|_|/ / | |/| | | |
* | | | | | Disable npm auditAleksey Kladov2020-07-021-3/+3
| |/ / / / |/| | | | | | | | | | | | | | At the moment it fails with unfixable minor vuln in a dev-dependency
* | | | | Merge #5149bors[bot]2020-07-018-71/+140
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5149: Implement Chalk variable kinds r=flodiebold a=flodiebold This means we need to keep track of the kinds (general/int/float) of variables in `Canonical`, which requires some more ceremony. (It also exposes some places where we're not really dealing with canonicalization correctly -- another thing to be cleaned up when we switch to using Chalk's types directly.) Should fix the last remaining issue of #2534. Co-authored-by: Florian Diebold <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 07:26:29 +0000