aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_editor
Commit message (Collapse)AuthorAgeFilesLines
...
* | fix testsgfreezy2018-12-251-1/+1
| |
* | add fix for removing unnecessary braces in use statementsgfreezy2018-12-253-23/+41
|/
* Merge #326bors[bot]2018-12-241-2/+54
|\ | | | | | | | | | | | | | | 326: resolved #324: remove unnecessary braces in use statement. r=matklad a=gfreezy Add inspection for unnecessary braces in use statement Co-authored-by: gfreezy <[email protected]>
| * keep severity to Error & WeakWarninggfreezy2018-12-241-9/+7
| |
| * add serverity to vscode diagnosticsgfreezy2018-12-231-8/+11
| |
| * resolved #324: remove unnecessary braces in use statement.gfreezy2018-12-231-2/+53
| |
* | Add make_pub_crate code action to ra_editorHirokazu Hata2018-12-242-2/+74
|/
* join lines collapses use_treesAleksey Kladov2018-12-211-0/+58
|
* fold curly blocksAleksey Kladov2018-12-201-15/+25
|
* generalize folding testsAleksey Kladov2018-12-201-21/+21
| | | | By using xml-like tags, we will be able to test nested foldings.
* rename Edit to TextEdit and AtomEdit to AtomTextEditBernardo2018-12-113-16/+21
|
* extract AtomEdit and Edit into new ra_text_edit crateBernardo2018-12-104-87/+4
|
* use \b as word boundaryBernardo2018-12-091-2/+30
|
* Implement and test format hookDJMcNab2018-12-091-1/+1
|
* find next whitespace or begining or endBernardo2018-12-081-3/+3
|
* Merge #264bors[bot]2018-12-081-1/+20
|\ | | | | | | | | | | | | | | 264: check for empty range when extending in comment r=matklad a=vemoo fix for #140 Co-authored-by: Bernardo <[email protected]>
| * check for empty range when extending in commentBernardo2018-12-081-1/+20
| |
* | Add a better text for hover and stop duplicating work done in ↵DJMcNab2018-12-081-0/+55
|/ | | | approximatelly_resolve_symbol
* modernize even moreAleksey Kladov2018-12-063-13/+5
|
* Merge #252bors[bot]2018-12-022-7/+44
|\ | | | | | | | | | | | | | | | | | | | | 252: Improve 'introduce variable' r=matklad a=flodiebold - make it possible to extract a prefix of an expression statement (e.g. `<|>foo.bar()<|>.baz()`) - don't turn the last expression in a block into a let statement - also fix a few typos Co-authored-by: Florian Diebold <[email protected]>
| * Improve 'introduce variable'Florian Diebold2018-12-022-7/+44
| | | | | | | | | | | | - make it possible to extract a prefix of an expression statement (e.g. <|>foo.bar()<|>.baz()) - don't turn the last expression in a block into a let statement
* | Add `derive` after doc commentsAleksey Kladov2018-12-021-5/+36
| |
* | Complete paths after ::Aleksey Kladov2018-11-211-6/+1
| |
* | cargo formatAdolfo Ochagavía2018-11-161-14/+98
| |
* | Rename col to col_utf16Adolfo Ochagavía2018-11-161-17/+17
| |
* | Support UTF-16 chars in LineIndexAdolfo Ochagavía2018-11-161-106/+197
|/
* Rename File -> SourceFileNodeAleksey Kladov2018-11-077-38/+51
|
* Rustfmt to pass CIJeremy A. Kolb2018-11-071-3/+9
|
* Show documentation for hover requestsJeremy A. Kolb2018-11-071-1/+25
|
* Merge #188bors[bot]2018-11-051-2/+10
|\ | | | | | | | | | | | | | | | | 188: Introduce `SyntaxErrorKind` and `TextRange` to `SyntaxError` r=matklad a=aochagavia Co-authored-by: Adolfo Ochagavía <[email protected]> Co-authored-by: Adolfo Ochagavía <[email protected]>
| * Introduce Location and make SyntaxError fields privateAdolfo Ochagavía2018-11-051-2/+10
| |
| * Introduce SyntaxErrorKind and TextRange in SyntaxErrorAdolfo Ochagavía2018-11-041-2/+2
| |
* | Introduce var works with tail exprsAleksey Kladov2018-11-051-11/+45
|/
* Remove DOC_COMMENTJeremy A. Kolb2018-10-311-1/+1
| | | | Closes #166
* Reformat allAleksey Kladov2018-10-313-11/+13
|
* remove old completionAleksey Kladov2018-10-315-1100/+1
|
* move resolve local nameAleksey Kladov2018-10-313-83/+2
|
* Move FnDescriptors to analyzerAleksey Kladov2018-10-311-1/+2
|
* Add ModuleScope as a queryAleksey Kladov2018-10-302-0/+8
| | | | | | | This is a first step towards queryifing completion and resolve. Some code currently duplicates ra_editor: the plan is to move all completion from ra_editor, but it'll take more than one commit.
* switch to TextRange::subrangeAleksey Kladov2018-10-301-2/+1
|
* Complete crate:: pathsAleksey Kladov2018-10-242-14/+18
|
* SimplifyAleksey Kladov2018-10-241-3/+1
|
* complete pub(crate)Aleksey Kladov2018-10-231-2/+8
|
* Restore folding import groupsAdolfo Ochagavía2018-10-231-6/+97
|
* Merge #138bors[bot]2018-10-226-18/+18
|\ | | | | | | | | | | | | | | | | | | | | | | 138: Fix some clippy lints r=matklad a=alanhdu I went ahead and fixed all the clippy lints (there were a couple I thought would be better unfixed and added `cfg` statements to allow them) and also re-enabled clippy and rustfmt in CI. They were disabled with `no time to explain, disable clippy checks`, so hopefully this won't go against whatever the reason at the time was :laughing:. One question about the CI though: right now, it's an allowed failure that runs against the latest nightly each time. Would it be better to pin it to a specific nightly (or use the `beta` versions) to lower the churn? Co-authored-by: Alan Du <[email protected]>
| * Rename new to new_item (to match new_impl)Alan Du2018-10-221-9/+9
| |
| * Revert "clippy: Fix new_ret_no_self"Alan Du2018-10-202-11/+11
| | | | | | | | This reverts commit 2ae9dfa812ccf18867373f77a106161378a6d91d.
| * Fix function callsAlan Du2018-10-181-1/+1
| |
| * clippy: Fix new_ret_no_selfAlan Du2018-10-182-11/+11
| |
| * clippy: Use if lets and remove redundant returnsAlan Du2018-10-183-7/+7
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 18:28:03 +0000