aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_assists
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge #762bors[bot]2019-02-102-0/+732
|\ | | | | | | | | | | | | | | | | | | | | | | | | 762: "Dumb" auto import assist r=matklad a=eulerdisk This adds a new assist to "add xxx::yyy to the current file" when the cursor is on a PATH. It manages correctly nested imports,`self` keyword and creates new nested imports if necessary. [See the tests] It doesn't use name resolution so in that sense is 'dumb', but I have plans to do that. That in the future will be useful to auto import trait names in autocompletion for example. It can easily be extended to provide multiple actions to select in which scope to import. That's another thing I plan to do. @matklad I copied some indentation code from `ide_light`, I don't know at the moment if/how you want to refactor that code. This assist was meant to be in `ide_light`. Co-authored-by: Andrea Pretto <[email protected]>
| * auto_import: use ra_fmtAndrea Pretto2019-02-091-109/+29
| |
| * auto_import: struct variants for ImportActionAndrea Pretto2019-02-091-44/+107
| |
| * auto_import: remove PathSegmentsMatchAndrea Pretto2019-02-092-66/+37
| |
| * auto_import: Removed Empty in favor of Partial(0)Andrea Pretto2019-02-091-16/+10
| | | | | | | | auto_import: Removed unecessary lifetimes
| * auto_import assistAndrea Pretto2019-02-093-0/+784
| |
* | Fix introduce var duplicating newlinesVille Penttinen2019-02-091-1/+80
|/ | | | | | | | | | | | | This fixes #713. If the block before the statement we want to use introduce var on, had empty lines these empty lines would also be added between the let-statement and the current line where the new variable is used. This fixes that by trimming excess newlines from the start of the indent chunk and simply adding a single newline (when the chunk had newlines) between the let-statement and the current statement. If there were no newlines this matches the previous behaviour.
* Merge #766bors[bot]2019-02-093-3/+3
|\ | | | | | | | | | | | | | | | | | | 766: Formatting code into ra_fmt r=matklad a=eulerdisk As discussed https://github.com/rust-analyzer/rust-analyzer/pull/762#discussion_r254905885 I did only move the code without other improvements. Co-authored-by: Andrea Pretto <[email protected]>
| * Refactor formatting code out of ra_ida_api_light into ra_fmt.Andrea Pretto2019-02-083-3/+3
| |
* | Improve sorting delegaterobojumper2019-02-091-7/+5
| |
* | Remove unused importrobojumper2019-02-081-2/+2
| |
* | Add tests for action target rangesrobojumper2019-02-0810-16/+210
| |
* | Add some assist rangesrobojumper2019-02-085-10/+58
|/
* reformat the worldAleksey Kladov2019-02-089-96/+27
|
* Remove unnecessary dbg! callsVille Penttinen2019-02-071-3/+2
|
* Add new assist to remove dbg!() callsVille Penttinen2019-02-072-0/+126
| | | | | | | | | | | | | | | | | This fixes #758. Currently we try to maintain the cursor position relative to the statement under cursor, if the cursor is inside the dbg! macro call. Meaning: let foo = dbg!(some.complex<|>().expression()); Should turn into: let foo = some.complex<|>().expression(); With the cursor staying in place.
* Some clippy cleanupskjeremy2019-02-061-3/+3
|
* assists: compute editkjeremy2019-02-061-1/+1
|
* move assists to a separate crateAleksey Kladov2019-02-0611-0/+1406