aboutsummaryrefslogtreecommitdiff
path: root/crates/ide_completion/src/completions
Commit message (Collapse)AuthorAgeFilesLines
* Don't take the parent kind of trailing attributes in attr completionLukas Wirth2021-05-311-3/+53
|
* Use `Name`s instead of Strings in the completion rendering apiLukas Wirth2021-05-315-30/+29
|
* Merge #9068bors[bot]2021-05-304-18/+41
|\ | | | | | | | | | | | | | | 9068: Move more `CompletinoContext` fields to `ImmediateLocation` r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Wirth <[email protected]>
| * Move more fields to `ImmediateLocation`Lukas Wirth2021-05-304-18/+41
| |
* | Fix incorrect prefer_inner calls on some attribute completionsLukas Wirth2021-05-301-6/+31
|/
* Only complete derive proc macros in `#[derive]`Jonas Schievink2021-05-291-2/+1
|
* Add some lint completion testsLukas Wirth2021-05-293-30/+67
|
* Merge #9027bors[bot]2021-05-293-359/+851
|\ | | | | | | | | | | | | | | | | | | | | 9027: feat: Attribute completion is context aware r=Veykril a=Veykril This splits off the `lint` and `derive` completions into their own submodules of `attribute`. The idea is to create a lazy global hashmap that maps `SyntaxKind` to attribute names(`&[&str]`) in which we index with the syntax kind of the "thing" we are attributing giving us the attributes back that are valid for this kind. Then we use this name to do a binary search on the attribute list to fetch and build the corresponding completion item. Co-authored-by: Lukas Wirth <[email protected]>
| * simplifyLukas Wirth2021-05-293-85/+92
| |
| * Add another attribute completion testLukas Wirth2021-05-281-5/+20
| |
| * Add attribute completion testsLukas Wirth2021-05-281-8/+399
| |
| * tt muncher timeLukas Wirth2021-05-273-27/+57
| |
| * Split attribute completion module into attribute, derive and lint modulesLukas Wirth2021-05-273-366/+302
| |
| * Attribute completion is context awareLukas Wirth2021-05-271-28/+141
| |
* | More completion pattern testsLukas Wirth2021-05-281-2/+0
| |
* | Implement prev sibling determination for `CompletionContext`Lukas Wirth2021-05-281-1/+1
| |
* | simplifyLukas Wirth2021-05-281-97/+95
| |
* | Complete keywords in (Assoc)ItemList with leading attributeLukas Wirth2021-05-281-0/+15
| |
* | Only complete modules in empty use-statementsLukas Wirth2021-05-281-14/+16
|/
* Complete modules in item listsLukas Wirth2021-05-273-4/+45
|
* Complete modules in assoc item listsLukas Wirth2021-05-272-4/+13
|
* Cleanup `ImmediateLocation` determinationLukas Wirth2021-05-272-3/+21
|
* Don't complete non-macro item paths in impls and modulesLukas Wirth2021-05-274-16/+56
|
* simplifyLukas Wirth2021-05-276-33/+27
|
* Collapse more CompletionContext booleans into enumsLukas Wirth2021-05-274-26/+21
|
* Set `record_pat_syntax` more precisely in CompletionContextLukas Wirth2021-05-261-8/+32
|
* Merge #9015bors[bot]2021-05-262-8/+9
|\ | | | | | | | | | | | | | | | | 9015: Merge pattern completion related bools into an enum r=Veykril a=Veykril The two bools can never both be set so this is basically just a tri-state enum. bors r+ Co-authored-by: Lukas Wirth <[email protected]>
| * Merge pattern completion related bools into an enumLukas Wirth2021-05-262-8/+9
| |
* | Merge #9012bors[bot]2021-05-261-21/+29
|\ \ | |/ |/| | | | | | | | | | | 9012: feat: add tab stops for keyword completions r=matklad a=eduardocanellas Add tab stops for all the keywords that I judged fit. I also introduced some line breaks and spaces, following the pattern I saw in the `postfix` module. Co-authored-by: Eduardo Canellas <[email protected]>
| * feat: add tab stops for keyword completionsEduardo Canellas2021-05-261-21/+29
| |
* | simplifyLukas Wirth2021-05-261-3/+3
|/
* fix: remove undesired completions from trait/impl blocksEduardo Canellas2021-05-261-0/+2
|
* fix: don't show pd/ppd completions where it shouldn't beEduardo Canellas2021-05-252-11/+5
|
* Paper over #8931 a bit moreFlorian Diebold2021-05-231-0/+1
| | | | | | | | | The problem was the skipping of binders in `resolve_method_call_as_callable`; this still doesn't use the _correct_ substitution, but at least it doesn't return a type with free variables in it. Fixes #8931.
* Add test for #8931 and better checkingFlorian Diebold2021-05-231-0/+29
|
* simplifyLukas Wirth2021-05-151-12/+10
|
* SimplifyEdwin Cheng2021-05-061-6/+2
|
* Fix: Do not overwrite comments and attrs in trait impl completionJesse Bakker2021-05-061-8/+65
|
* simplifyLukas Tobias Wirth2021-05-053-8/+9
|
* Add some cov marks for qualified_path completionLukas Tobias Wirth2021-05-041-5/+8
|
* Complete enum variants through type aliasesLukas Tobias Wirth2021-05-041-7/+33
|
* Make CompletionContext expected_type smarterLukas Tobias Wirth2021-05-031-22/+0
|
* Fix feature description inconsistencyBrandon2021-05-011-1/+1
|
* Add cov_marks to insert_use testsLukas Wirth2021-04-201-1/+1
|
* Exclude inherent traits from flyimportsKirill Bulatov2021-04-161-0/+23
|
* Do not show flyimports in trait or impl declarationsKirill Bulatov2021-04-151-0/+50
|
* Fix typomemoryruins2021-04-071-2/+2
|
* Do not import on the fly during fields of record literal syntaxmemoryruins2021-04-061-0/+43
|
* Resolve associated typesLukas Wirth2021-04-011-1/+1
|
* Merge #8267bors[bot]2021-03-311-0/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8267: Adding gifs and screenshots for features in manual r=matklad a=MozarellaMan For #6539 This includes most of gif or screenshot examples of most items in the "Features" header. With the exceptions of: - **On Typing Assists** - couldn't get it to work for a demo, I'm probably missing something? - **Structural search and replace** - looked to be already a visual example of the feature - **Workspace symbol** - wasn't sure how best to show this, all of the examples maybe? Also wasn't sure of the best code example to show it off - **Semantic Syntax Highlighting** - seemed obvious enough to not need a screenshot, but I could easily add this All the gifs/pngs are hosted in this [comment](https://github.com/rust-analyzer/rust-analyzer/issues/6539#issuecomment-809574840). Please let me know if any of them aren't suitable (and why) and I'll improve it! Or if you don't like the theme/font Co-authored-by: Ayomide Bamidele <[email protected]>