rust/crates/completion/src/lib.rs

286 lines
9.5 KiB
Rust
Raw Normal View History

//! `completions` crate provides utilities for generating completions of user input.
2020-10-25 02:59:15 -05:00
mod config;
mod item;
mod context;
2020-07-04 11:53:30 -05:00
mod patterns;
mod generated_lint_completions;
2020-07-04 11:53:30 -05:00
#[cfg(test)]
mod test_utils;
2020-11-01 03:35:04 -06:00
mod render;
2019-01-08 13:33:36 -06:00
2020-10-25 02:59:15 -05:00
mod completions;
2019-01-08 13:33:36 -06:00
2020-12-04 08:03:22 -06:00
use ide_db::{
base_db::FilePosition, helpers::insert_use::ImportScope, imports_locator, RootDatabase,
};
use syntax::AstNode;
use text_edit::TextEdit;
2019-01-08 13:33:36 -06:00
use crate::{completions::Completions, context::CompletionContext, item::CompletionKind};
2019-01-08 13:33:36 -06:00
pub use crate::{
config::{CompletionConfig, CompletionResolveCapability},
2020-12-04 02:02:22 -06:00
item::{CompletionItem, CompletionItemKind, CompletionScore, ImportEdit, InsertTextFormat},
};
2019-01-08 13:33:36 -06:00
//FIXME: split the following feature into fine-grained features.
// Feature: Magic Completions
//
// In addition to usual reference completion, rust-analyzer provides some ✨magic✨
// completions as well:
//
// Keywords like `if`, `else` `while`, `loop` are completed with braces, and cursor
// is placed at the appropriate position. Even though `if` is easy to type, you
// still want to complete it, to get ` { }` for free! `return` is inserted with a
// space or `;` depending on the return type of the function.
//
// When completing a function call, `()` are automatically inserted. If a function
// takes arguments, the cursor is positioned inside the parenthesis.
//
// There are postfix completions, which can be triggered by typing something like
// `foo().if`. The word after `.` determines postfix completion. Possible variants are:
//
// - `expr.if` -> `if expr {}` or `if let ... {}` for `Option` or `Result`
// - `expr.match` -> `match expr {}`
// - `expr.while` -> `while expr {}` or `while let ... {}` for `Option` or `Result`
// - `expr.ref` -> `&expr`
// - `expr.refm` -> `&mut expr`
// - `expr.let` -> `let <|> = expr;`
// - `expr.letm` -> `let mut <|> = expr;`
// - `expr.not` -> `!expr`
// - `expr.dbg` -> `dbg!(expr)`
2020-10-14 08:23:51 -05:00
// - `expr.dbgr` -> `dbg!(&expr)`
// - `expr.call` -> `(expr)`
//
// There also snippet completions:
//
// .Expressions
2020-07-19 11:25:19 -05:00
// - `pd` -> `eprintln!(" = {:?}", );`
// - `ppd` -> `eprintln!(" = {:#?}", );`
//
// .Items
// - `tfn` -> `#[test] fn feature(){}`
// - `tmod` ->
// ```rust
// #[cfg(test)]
// mod tests {
// use super::*;
//
// #[test]
// fn test_name() {}
// }
// ```
2020-11-24 16:42:58 -06:00
//
2020-12-08 06:27:18 -06:00
// And the auto import completions, enabled with the `rust-analyzer.completion.autoimport.enable` setting and the corresponding LSP client capabilities.
// Those are the additional completion options with automatic `use` import and options from all project importable items,
// fuzzy matched agains the completion imput.
2019-01-08 13:33:36 -06:00
/// Main entry point for completion. We run completion as a two-phase process.
///
/// First, we look at the position and collect a so-called `CompletionContext.
/// This is a somewhat messy process, because, during completion, syntax tree is
/// incomplete and can look really weird.
///
/// Once the context is collected, we run a series of completion routines which
2019-02-11 10:18:27 -06:00
/// look at the context and produce completion items. One subtlety about this
2019-01-08 13:33:36 -06:00
/// phase is that completion engine should not filter by the substring which is
/// already present, it should give all possible variants for the identifier at
/// the caret. In other words, for
///
2020-08-22 14:03:02 -05:00
/// ```no_run
2019-01-08 13:33:36 -06:00
/// fn f() {
/// let foo = 92;
/// let _ = bar<|>
/// }
/// ```
///
/// `foo` *should* be present among the completion variants. Filtering by
/// identifier prefix/fuzzy match should be done higher in the stack, together
/// with ordering of completions (currently this is done by the client).
pub fn completions(
2020-03-10 12:39:17 -05:00
db: &RootDatabase,
2020-03-31 09:02:55 -05:00
config: &CompletionConfig,
2020-05-17 05:09:53 -05:00
position: FilePosition,
2020-03-10 12:39:17 -05:00
) -> Option<Completions> {
2020-03-31 09:02:55 -05:00
let ctx = CompletionContext::new(db, position, config)?;
2019-01-08 13:33:36 -06:00
2020-10-12 02:59:15 -05:00
if ctx.no_completion_required() {
// No work required here.
return None;
}
2019-01-08 13:33:36 -06:00
let mut acc = Completions::default();
2020-10-25 02:59:15 -05:00
completions::attribute::complete_attribute(&mut acc, &ctx);
completions::fn_param::complete_fn_param(&mut acc, &ctx);
completions::keyword::complete_expr_keyword(&mut acc, &ctx);
completions::keyword::complete_use_tree_keyword(&mut acc, &ctx);
completions::snippet::complete_expr_snippet(&mut acc, &ctx);
completions::snippet::complete_item_snippet(&mut acc, &ctx);
completions::qualified_path::complete_qualified_path(&mut acc, &ctx);
completions::unqualified_path::complete_unqualified_path(&mut acc, &ctx);
completions::dot::complete_dot(&mut acc, &ctx);
completions::record::complete_record(&mut acc, &ctx);
completions::pattern::complete_pattern(&mut acc, &ctx);
completions::postfix::complete_postfix(&mut acc, &ctx);
completions::macro_in_item_position::complete_macro_in_item_position(&mut acc, &ctx);
completions::trait_impl::complete_trait_impl(&mut acc, &ctx);
completions::mod_::complete_mod(&mut acc, &ctx);
Some(acc)
2019-01-08 13:33:36 -06:00
}
2020-12-04 08:03:22 -06:00
/// Resolves additional completion data at the position given.
pub fn resolve_completion_edits(
db: &RootDatabase,
config: &CompletionConfig,
position: FilePosition,
full_import_path: &str,
imported_name: &str,
2020-12-06 15:58:15 -06:00
) -> Option<Vec<TextEdit>> {
2020-12-04 08:03:22 -06:00
let ctx = CompletionContext::new(db, position, config)?;
let anchor = ctx.name_ref_syntax.as_ref()?;
let import_scope = ImportScope::find_insert_use_container(anchor.syntax(), &ctx.sema)?;
let current_module = ctx.sema.scope(anchor.syntax()).module()?;
let current_crate = current_module.krate();
let import_path = imports_locator::find_exact_imports(&ctx.sema, current_crate, imported_name)
.filter_map(|candidate| {
let item: hir::ItemInNs = candidate.either(Into::into, Into::into);
current_module.find_use_path(db, item)
})
.find(|mod_path| mod_path.to_string() == full_import_path)?;
2020-12-06 15:58:15 -06:00
ImportEdit { import_path, import_scope, merge_behaviour: config.merge }
.to_text_edit()
.map(|edit| vec![edit])
2020-12-04 08:03:22 -06:00
}
#[cfg(test)]
mod tests {
2020-10-25 02:59:15 -05:00
use crate::config::CompletionConfig;
use crate::test_utils;
struct DetailAndDocumentation<'a> {
detail: &'a str,
documentation: &'a str,
}
2020-07-01 10:08:45 -05:00
fn check_detail_and_documentation(ra_fixture: &str, expected: DetailAndDocumentation) {
let (db, position) = test_utils::position(ra_fixture);
let config = CompletionConfig::default();
let completions: Vec<_> = crate::completions(&db, &config, position).unwrap().into();
for item in completions {
if item.detail() == Some(expected.detail) {
let opt = item.documentation();
let doc = opt.as_ref().map(|it| it.as_str());
assert_eq!(doc, Some(expected.documentation));
return;
}
}
panic!("completion detail not found: {}", expected.detail)
}
2020-10-12 02:59:15 -05:00
fn check_no_completion(ra_fixture: &str) {
let (db, position) = test_utils::position(ra_fixture);
2020-10-12 02:59:15 -05:00
let config = CompletionConfig::default();
let completions: Option<Vec<String>> = crate::completions(&db, &config, position)
.and_then(|completions| {
let completions: Vec<_> = completions.into();
if completions.is_empty() {
None
} else {
Some(completions)
}
})
2020-10-12 02:59:15 -05:00
.map(|completions| {
completions.into_iter().map(|completion| format!("{:?}", completion)).collect()
});
// `assert_eq` instead of `assert!(completions.is_none())` to get the list of completions if test will panic.
assert_eq!(completions, None, "Completions were generated, but weren't expected");
}
#[test]
fn test_completion_detail_from_macro_generated_struct_fn_doc_attr() {
check_detail_and_documentation(
r#"
//- /lib.rs
macro_rules! bar {
() => {
struct Bar;
impl Bar {
#[doc = "Do the foo"]
fn foo(&self) {}
}
}
}
bar!();
fn foo() {
let bar = Bar;
bar.fo<|>;
}
"#,
DetailAndDocumentation { detail: "fn foo(&self)", documentation: "Do the foo" },
);
}
#[test]
fn test_completion_detail_from_macro_generated_struct_fn_doc_comment() {
check_detail_and_documentation(
r#"
//- /lib.rs
macro_rules! bar {
() => {
struct Bar;
impl Bar {
/// Do the foo
fn foo(&self) {}
}
}
}
bar!();
fn foo() {
let bar = Bar;
bar.fo<|>;
}
"#,
DetailAndDocumentation { detail: "fn foo(&self)", documentation: " Do the foo" },
);
}
2020-10-12 02:59:15 -05:00
#[test]
fn test_no_completions_required() {
// There must be no hint for 'in' keyword.
2020-10-12 02:59:15 -05:00
check_no_completion(
r#"
fn foo() {
for i i<|>
}
"#,
);
// After 'in' keyword hints may be spawned.
check_detail_and_documentation(
r#"
/// Do the foo
fn foo() -> &'static str { "foo" }
fn bar() {
for c in fo<|>
}
"#,
DetailAndDocumentation {
detail: "fn foo() -> &'static str",
documentation: "Do the foo",
},
);
2020-10-12 02:59:15 -05:00
}
}